SOLVED

Receiving Error: Issuer should match tenants domainName for non federated identity - Azure AD B2C

%3CLINGO-SUB%20id%3D%22lingo-sub-2885833%22%20slang%3D%22en-US%22%3EReceiving%20Error%3A%20Issuer%20should%20match%20tenants%20domainName%20for%20non%20federated%20identity%20-%20Azure%20AD%20B2C%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2885833%22%20slang%3D%22en-US%22%3E%3CP%3ERecently%2C%20we%20started%20receiving%20the%20error%20%3A%26nbsp%3B%20%3CSTRONG%3EIssuer%20should%20match%20tenants%20domainName%20for%20non%20federated%20identity%26nbsp%3B%3C%2FSTRONG%3Ewhen%20attempting%20to%20create%20a%20B2C%20user%20via%20a%20.net%20core%20app%20hosted%20in%20azure.%26nbsp%3B%20No%20changes%20have%20been%20made%20to%20the%20configuration%20or%20code.%26nbsp%3B%20%26nbsp%3BThe%20same%20setup%20and%20code%20is%20working%20in%20a%20different%20app%20pointing%20to%20a%20different%20B2C%20instance.%26nbsp%3B%20The%20only%20differences%20are%20the%20specifics%20for%20tenantId%2C%20applicationId%2C%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3BI've%20compared%20the%20working%20instance%20with%20the%20non-working%20instance%2C%20and%20cannot%20find%20any%20configuration%20differences%20between%20the%20ADB2C%20instances%2C%20Azure%20App%20Services%2C%20security%20or%20configuration%20items%2C%20other%20than%20the%20aforementioned%20items%20specific%20to%20each%20instance.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20encountered%20this%20error%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMike.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2890281%22%20slang%3D%22en-US%22%3ERe%3A%20Receiving%20Error%3A%20Issuer%20should%20match%20tenants%20domainName%20for%20non%20federated%20identity%20-%20Azure%20AD%20B2%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2890281%22%20slang%3D%22en-US%22%3E%3CP%3EI%20wasn't%20able%20to%20figure%20out%20exactly%20why%20this%20was%20happening%2C%20but%20I%20did%20find%20a%20resolution%20and%20thought%20I'd%20update%20this%2C%20just%20in%20case%20someone%20else%20ever%20runs%20into%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20whatever%20reason%2C%20deleting%20the%20Azure%20App%20Service%20and%20recreating%20it%20resolved%20the%20issue.%26nbsp%3B%20I%20used%20the%20exact%20same%20configuration%20as%20before%20and%20redeployed%20the%20exact%20same%20code.%26nbsp%3B%20I'm%20no%20longer%20receiving%20the%20error.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Recently, we started receiving the error :  Issuer should match tenants domainName for non federated identity when attempting to create a B2C user via a .net core app hosted in azure.  No changes have been made to the configuration or code.   The same setup and code is working in a different app pointing to a different B2C instance.  The only differences are the specifics for tenantId, applicationId, etc.

 

 I've compared the working instance with the non-working instance, and cannot find any configuration differences between the ADB2C instances, Azure App Services, security or configuration items, other than the aforementioned items specific to each instance.

 

Has anyone encountered this error? 

 

Thanks,

 

Mike.

1 Reply
best response confirmed by mrohrs (New Contributor)
Solution

I wasn't able to figure out exactly why this was happening, but I did find a resolution and thought I'd update this, just in case someone else ever runs into this.

 

For whatever reason, deleting the Azure App Service and recreating it resolved the issue.  I used the exact same configuration as before and redeployed the exact same code.  I'm no longer receiving the error.