web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Service | Customer Service, Contact Center, Fie...
Suggested Answer

MS Dynamics implementation is down- no clue where to look: [CrmSecurityException: Relying Party Certificate was not found.]

(0) ShareShare
ReportReport
Posted on by 10

Hi everyone, 

I've inherited an old MSCRM implementation at a new job that has not been working for some time. I suspect that it's an issue with an expired certificate, that was used for ADFS. However, having replaced that certificate I'm still getting errors. This is the error we get when trying to browse to the URL of Dynamics:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Relying Party Certificate was not found. 
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: Microsoft.Crm.CrmSecurityException: Relying Party Certificate was not found.

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Stack Trace: 


[CrmSecurityException: Relying Party Certificate was not found.]
   Microsoft.Crm.Authentication.Claims.ClaimsUtility.GetServiceConfiguration()  1737
   Microsoft.Crm.Authentication.Claims.CrmFederatedAuthenticationModule.SetDefaults()  719
   System.Web.HttpApplication.InitModulesCommon()  202
   System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers)  1089
   System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context)  232
   System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)  426
 


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.4110.0 

In IIS, having browsed to the Dynamics site, as well as the default site, the bindings look correct and associate :443/https with the correct cert. No matter what cert, or combination of certs that I use, produce the same error. 

When I look in "AD FS 2.0" manager, I browse down to "Trust relationships -> relying party trusts" and I see 2 entries. Both show as having red x's next to them. So obviously this seems like a problem area, but I'm not sure what to do, as I am quite novice when it comes to Dynamics and ADFS as  a whole. When right clicking, I get the option to "Update from federation Metadata", but am given the error in the image below. I do have the option to add/create a new Relying Part Trust, but I do not know how to associate this with the dynamics page. Specifically I don't know what to use for the "Federation metadata address (host name or URL). Our URL to access crm is "crm.domain.com" with the main landing page being "crm.domain.com/main.aspx". 

Any information here would be helpful. 

Thank you

pastedimage1672416824121v1.png

I have the same question (0)
  • PerezAguiar Profile Picture
    Microsoft Employee on at

    Hey!

    I understand that when you're checking ADFS 2.0, this is on another server, right?  What happens if you browse to the CRM Locally (http://localhost:port). 

    Regards,

  • Suggested answer
    Pedro Cadavez de Freitas Profile Picture
    on at

    Hello d34db33f ,

    Hope you are well.

    If you cannot update from CRM federation metadata, you should focus there as there should be a mismatch then between the cert info stored on ADFS Relying party trust and the one used on CRM IIS.

    The most standard reason why Federation Metadata cannot be updated is due to a TLS communication problem between ADFS and CRM.

    Please test first trying to run that federation URL on a browser on ADFS server.

    I would focus on first enabling all TLS cyphers on both CRM and ADFS to make sure they are both communicating and then move from there.

    You can use a tool from www.nartac.com/.../,  to quickly check that.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 45 Super User 2025 Season 2

#2
Daniyal Khaleel Profile Picture

Daniyal Khaleel 27 Most Valuable Professional

#3
Soundari Profile Picture

Soundari 15

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans