Since I have no immediate need to get this fixed, my goal is to merely start a discussion around if others have had this problem and if Microsoft agrees that the issuer in the metadoc from should be updated to sts.windows. That's kind of the whole point of having the metadoc endpoint Ideally, all configuration would come from the meta doc. I can get around this by configuring (hard-coding) valid issuers in my JwtBearer auth handler. However, the authorize endpoint domain is and, this is no longer the preferred authorization host, in favor of per this blog post. When configured with this meta doc, the token and meta doc issuers correctly match. Azure mobile app Stay connected to your Azure resourcesanytime, anywhere. The standard authentication handler balks at this, as it should. Sign in New to Azure Start free Check out the how-to video series for tips on deploying your cloud workloads from the Azure portal. However, the issuer in the token does not match the issuer in the metadoc. I'm able to make authorize requests to the authorization_endpoint in the doc and be issued valid tokens. I got my openid connect meta doc from the App Registrations > Endpoints panel in the Azure portal: I'm setting up some app registrations with Azure AD.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |