Search This Blog

Thursday, August 23, 2018

Dynamics CRM : The issuer of the security token was not recognized by the IssuerNameRegistry

Error:
When attempting to login IFD CRM

 An unhandled exception has occurred. 
  
 ed99eb103fdf430ba37f7e21aefb7aee102/LM/W3SVC/2/ROOT-1-131794808829640396 
   Full    C:\Program Files\Microsoft Dynamics CRM\CRMWeb\ CRM_SRV 
    
   8424 
   w3wp.exe 
    
   SecurityTokenException 
   ID4175: The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this issuer, configure the IssuerNameRegistry to return a valid name for this issuer. at System.IdentityModel.Tokens.SamlSecurityTokenHandler.ValidateToken(SecurityToken token) at System.IdentityModel.Services.TokenReceiver.AuthenticateToken(SecurityToken token, Boolean ensureBearerToken, String endpointUri) at System.IdentityModel.Services.WSFederationAuthenticationModule.SignInWithResponseMessage(HttpRequestBase request) at System.IdentityModel.Services.WSFederationAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args) at Microsoft.Crm.Authentication.Claims.CrmFederatedAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs args) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)  
   
   /default.aspx

Solution:
1) Open deployment manager and Rerun the config claim based Authentication(Note:Choose valid certificate)
2)Open ADFS console management
3) In the left pane, select the certificates and right click and select Set Service Communication Certificates
4) Choose the valid certificate(one you choose in deployment manage).
5) Update the relaying party trust
6) Restart ADFS and IIS

Kindly refer this blog below:
http://www.interactivewebs.com/blog/index.php/server-tips/microsoft-crm-2011-exception-message-id4175-the-issuer-of-the-security-token-was-not-recognized-by-the-issuernameregistry/