logo
down
shadow

Not getting upn (unique principal name) in claims in Azure AD authentication


Not getting upn (unique principal name) in claims in Azure AD authentication

By : user2952944
Date : November 19 2020, 03:59 PM
it helps some times You will get UPN in claims only if you are the user of that Azure Active Directory if you are listing as other user to that directory, you will not get UPN in claims.
For experiment you can create a user in the directory with "New user in your Organization" as Type of User and then try login in with new user and see you will get UPN now.
code :


Share : facebook icon twitter icon
Azure Mobile App Authentication With Custom Role Claims - Claims Disappearing

Azure Mobile App Authentication With Custom Role Claims - Claims Disappearing


By : Angel Torres
Date : October 22 2020, 02:00 PM
seems to work fine I've got a chapter on this in the book - https://adrianhall.github.io/develop-mobile-apps-with-csharp-and-azure/chapter2/custom/#using-third-party-tokens
Note the bit about custom authentication with additional claims. You need to call a custom API with the original token, check the token for validity, then produce a new token (the zumo token) with the claims you want. You can then use those claims for anything that is required.
How to disable storing of claims principal records in Azure B2C?

How to disable storing of claims principal records in Azure B2C?


By : user2086601
Date : March 29 2020, 07:55 AM
this will help Azure B2C stores information about every claims principal logged in. We do not need this information. Users should be just passed through B2C from IdPs to service provider. How to disable storing users information in B2C? , Here is the solution I found. The base policy in SignIn userjourney
code :
<UserJourney Id="SignIn">
    <OrchestrationStep Order="4" Type="ClaimsExchange">
      <Preconditions>
        <Precondition Type="ClaimsExist" ExecuteActionsIf="true">
          <Value>objectId</Value>
          <Action>SkipThisOrchestrationStep</Action>
        </Precondition>
      </Preconditions>
      <ClaimsExchanges>
        <ClaimsExchange Id="AAD-UserWriteUsingAlternativeSecurityId" TechnicalProfileReferenceId="AAD-UserWriteUsingAlternativeSecurityId" />
      </ClaimsExchanges>
    </OrchestrationStep>
TechnicalProfileReferenceId="AAD-UserReadUsingAlternativeSecurityId-NoError"
System.Security.Principal.WindowsIdentity (User.Identity) fails to populate the claims as sent by Azure AD

System.Security.Principal.WindowsIdentity (User.Identity) fails to populate the claims as sent by Azure AD


By : Dave Stronghold
Date : March 29 2020, 07:55 AM
will help you the issue in my application was because of the behavior of Owin, the middleware I used in my application.
Issue with the Owin: In OWIN, the response headers collection is the primary storage location for response cookies. System.Web however stores response cookies in a separate HttpContext.Response.Cookies collection and then writes them out to the Response.Headers collection just before sending the response. This can cause a conflict if OWIN if both approaches are used on the same request, as the Response.Cookies collection will overwrite any cookies set via the OWIN response headers.
Getting access token claims in claims principal in IdentityServer4

Getting access token claims in claims principal in IdentityServer4


By : Devon Gulley
Date : March 29 2020, 07:55 AM
I hope this helps you . The question is kind of invalid, but I'll leave it here with reasons why and a solution to save others time.
Firstly, there are two tokens for two different purposes.
Azure Service principal authentication for API App

Azure Service principal authentication for API App


By : Edc Bhurfv
Date : March 29 2020, 07:55 AM
fixed the issue. Will look into that further You can't acquire the token from front-end with client credentials.
Instead you must use the Implicit Grant Flow to get the access token in a fragment after a redirect, or pass it to the front-end from the backend of your app.
shadow
Privacy Policy - Terms - Contact Us © ourworld-yourmove.org