unexpected – CRM Kitchen http://crmkitchen.com Microsoft Dynamic CRM Tue, 25 Oct 2016 14:58:06 +0000 en-US hourly 1 https://wordpress.org/?v=4.6.1 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 http://crmkitchen.com/issuer-security-token-not-recognized-issuernameregistry-accept-security-tokens-issuer-configure-issuernameregistry-return-valid-name-issuer/ http://crmkitchen.com/issuer-security-token-not-recognized-issuernameregistry-accept-security-tokens-issuer-configure-issuernameregistry-return-valid-name-issuer/#respond Mon, 26 Sep 2016 12:46:39 +0000 http://crmkitchen.com/?p=309 If you get an error like this, you have to update federation metedata url and iisreset then restart adfs service.  Normally CRM throws a generic error and I found this message from trace. The issuer of the security token was not recognized by the IssuerNameRegistry. To accept security tokens from this issuer, configure the IssuerNameRegistry to […]

The post 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 appeared first on CRM Kitchen.

]]> If you get an error like this, you have to update federation metedata url and iisreset then restart adfs service.  Normally CRM throws a generic error and I found this message from trace.

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

unexpected-error-crm

  1. Open Deployment Manager on CRM Server
  2. Configure Claims Based Authentication from wizard
  3. Click start menu, select run and type iisreset to complete.
  4. Then go to Services on ADFS Server and restart ADFS Service.

 

Reference : https://support.microsoft.com/en-us/kb/2686840

http://www.dynamicscrmpros.com/microsoft-dynamics-crm-error-the-issuer-of-the-security-token-was-not-recognized-by-the-issuernameregistry-solved/

The post 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 appeared first on CRM Kitchen.

]]> http://crmkitchen.com/issuer-security-token-not-recognized-issuernameregistry-accept-security-tokens-issuer-configure-issuernameregistry-return-valid-name-issuer/feed/ 0