Skip to main content

Hi

After configuring oauth and the claims issuer in designer I am unable to log in fully to designer using my AAD account, redirects fine to the Azure login but after this I get the error

 

WIF10201: No valid key mapping found for securityToken: 'System.IdentityModel.Tokens.X509SecurityToken' and issuer: 'https://sts.windows.net/xxxx-xxxx-xxxxx

 

I have checked the Thumbprint against the accesscontrol.windows.net certificate and this seems fine, I believe this to be the current 92B88C3DD981BF1EBCB244FCFA63C007706C79E0, a couple of alkthroughs had used this one 3464C5BDD2BE7F2B6112E2F08E9C0024E33D9FE but I believe that to be expired now.

 

Has anyone else had a similar issue.

 

Thanks

 

Adam

 

 

Hi AdamBryant,

 

I haven't had specific experience with azure AD, but this sounds just like a traditional claims config issue.  Check the documentation here: http://help.k2.com/onlinehelp/k2blackpearl/icg/current/webframe.html#claims_oauth_configuration.html

That doc gives the location of the smartforms responsible for claims authentication.  From the message it seems that there is a mapping that is not there for the token issuer.

 

Make sure your issuer exists (htts://sts.windows.net/xxxx-xxxx-xxxx), if not, add it using the Identity.AddIssuer form, and make sure a valid mapping exists for it in AddClaimType mapping.

 

If you want to post screenshots of the relavent forms and entries, I'll see if my non azure knowledge translates.

 

Regards,

 

Mike

 

PS.  Posting your actual thumbprint may not be a good idea.  Just make sure it matches.


Verify that you have trailing slash in Claims Issuers Issuer value like shown on the picture below (i.e. it should have that slash shown in red on the screenshot in the very end of the issuer URL):


 


10840iFB0F251B033B4146.png


 


I've seen error exactly because of missing slash in this place. Note my screenshot shows: https://sts.windows.net for initial part of Issuer URL, but it is better use https://login.microsoftonline.com instead (I believe MSFT replaces that sts.windows net URL with https://login.microsoftonline.com and you should always use it).


Reply