claims-based-identity

来源： https://stackoverflow.com/questions/52555722/azure-ad-issues-claims-security-groups-names

来源： https://stackoverflow.com/questions/51119926/jwt-authentication-usermanager-getuserasync-returns-null

来源： https://stackoverflow.com/questions/51119926/jwt-authentication-usermanager-getuserasync-returns-null

问题 So, I was having trouble with Bearer authentication while setting up IdentityServer4. Basically, I wasn't able to call my API resource and was getting a 401 error. When I added the Authorization header with the access_token. I was able to get the data from my web request. using (var client = new HttpClient()) { client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", authToken); var content = await client.GetStringAsync("http://localhost:5000/localapi"); } The way

问题 When a user is signing-up in the system, he is automatically redirected to our application as a signed in user. I would like that after the sign-up, he is redirected to the signing page. I want this behavior since users need to be approved by an admin before having access to the system. I use custom policies. I tried to use the "SM-Noop" session manager but it is not working. There is my code: <!--Local account sign-up page--> <TechnicalProfile Id="LocalAccountSignUpWithLogonEmail">

问题 I followed this article where it explains how to implement a custom policy using Active Directory B2C. Everything is working great, the only concern I have is that the custom claim is returned like a serialized object. Let me explain a little bit better. I successfully created the Azure Function which return the custom claim. The encoded resulting JWT is like the following (please focus on the " userPermissions " value): { "exp": 1594560277, "nbf": 1594556677, "ver": "1.0", "auth_time":

问题 I have three applications in my solution, all built in asp.net core 1 MVC 6. App 1 is an MVC app used for authenticating a user. App 2 is an Angular SPA app and is the main app in the solution. App 3 is an MVC web api application. In app 3, I have the usual asp.net core SignInManager and UserManager code (the same code as you get by default when you start a new MVC 6 template - only different is, it exists in my web api here). And the login/logout/register etc is exposed via web api methods

问题 I am trying to move away from WebForms and learn MVC, specifically using the new ASP.NET Identity model. However, I cant seem to find any formal documentation from Microsoft, that demonstrates how to create a claims object, and store it in a database for a authenticated user. My site, needs to do the following: Authentication a user - TICK Create a Claim, and store user information in it, so that I can use it throughout the session - NO TICK Pull back the users roles from the new ASP.NET

问题 Let's say I have the following roles: Admin User I want Admin role to impersonate specific user account with User role, but without knowing that specific user account's password. Admin should be able to impersonate any user from the application and be able to browse the application as the user himself. I found a link where this is actually implemented in ASP.NET MVC 4.6, but having a little headaches while converting this to Core version. Mostly because of the last line of code in the link

问题 Let's say I have the following roles: Admin User I want Admin role to impersonate specific user account with User role, but without knowing that specific user account's password. Admin should be able to impersonate any user from the application and be able to browse the application as the user himself. I found a link where this is actually implemented in ASP.NET MVC 4.6, but having a little headaches while converting this to Core version. Mostly because of the last line of code in the link