Activities of "maliming"

hi

The role type in claims is ClaimTypes.Role(http://schemas.microsoft.com/ws/2008/06/identity/claims/role)

Please check the typeValue of AbpClaimTypes.Role

var typeValue = AbpClaimTypes.Role typeValue should be http://schemas.microsoft.com/ws/2008/06/identity/claims/role

 {
 "Type": "http://schemas.microsoft.com/ws/2008/06/identity/claims/role",
 "Value": "admin"
 }

If the typeValue is role, that's mean your claim type is incorrect.

Please also check the Roles of CurrentUser, if the Roles is empty, it is also the problem of claim type.

Thanks.

hi I have checked your angular app.

The angular should init the code flow and redirect to autherver website.

This is the default behavior of abp angular app.

angular app -> click login button -> redirect to authserver website(login page.).

Can you check your app to make this?

hi

Let me see your code. But I think you still need to reproduce the problem in the end.

Please join and share your screen.

Thanks https://us05web.zoom.us/j/86954384800?pwd=rqxIqOwttMkgIKuAKD86w3KilGRFzO.1

hi

This issue is highly escalated into our organization and we certainly need you to look into this matter and provide support to resolve it.

Can you ask other colleagues if they can reproduce the problem?

I have explained a lot of the content of the problem.

References: https://abp.io/support/questions/8267/Tenant-Id-and-Tenant-Name-Not-Set-in-Header-After-Dashboard-Redirect-SSO-OIDC?CurrentPage=2#answer-3a163ae6-c2bb-7256-cbd1-03ecdb09add8 https://abp.io/support/questions/8267/Tenant-Id-and-Tenant-Name-Not-Set-in-Header-After-Dashboard-Redirect-SSO-OIDC?CurrentPage=2#answer-3a163adf-89f4-6c29-5e28-87e18a775dd7

hi

Remote troubleshooting will take too much time, especially under poor network conditions. This can be avoided. Because your problem has nothing to do with your microservices project.

I can't do this directly without permission, and I don't think they will allow me to proceed with this approach.

The code you share will not contain any secrets. It's a simple Angular app and an auth server project with an external login provider.

You can create an open-source (app instead of app-pro) template project and add your code.

ok, You can create a private GitHub repo and invite me as a contributor.

https://github.com/maliming

hi

This has nothing to do with microservice.

Only need two projects:

1. angular
2. auth server(add oauth0.com as external login)

Angular tries to log in and get the token. That's all.

hi

I have got your project.

Can you share some steps to show the problem?

Or what code you don't understand? etc...

Then I will add a new code.

Thanks.

hi

You don't need the entire project, you can try copying part of the code in your project to the POC project to reproduce the problem, I will check the POC project , this is just the login code, it should be simple.

Thanks.

There are two oauth2 processes:

1. angular request to login (redirect is localhost:4200) , redirect to auth server(your API website)
2. your auth server request to login, redirect to oauth0.com (redirect is localhost:44359, the redirect url also includes the angular request.)
3. after login in oauth.com -> redirect to auth server( because redirect is localhost:44359)
4. re-request angular request(redirect is localhost:4200)
5. because you have login success. then generate code and redirect to localhost:4200?code=123123
6. angular get the code , and use the code to exchange the access_token.

1. The angular need to codeget access token from auth server
2. The auth server need to login to return the code
3. The auth server can login with oauth0.com
4. After login with oauth0.com, The auth server has login state.
5. The auth server now can return a code to angular
6. The angular use the code to get access token from auth server