Activities of "Repunjay_TASC"

you successfully redirected to dashboard right ?

add call back url "CallbackPath": "/api/oidc/ExternalLoginCallback" SSOAppTemplate.AuthServer appsetting.json

SSOAppTemplateAuthServerModule.cs file add below line inside ConfigureServices method

options.CallbackPath = configuration["Authentication:OpenIDConnect:CallbackPath"];

ok give me 5 mint

The log does not contain the internal exception.

The logs of this 500 error should exist on the project, which depends on the AbpAccountPublicApplicationModule(Volo.Abp.Account.Pro.Public.Application) module.

[14:10:09 INF] [] Request starting "HTTP/2" "GET" "https"://"localhost:44359""""/api/account/my-profile""" - null null  
[14:10:09 INF] [] CORS policy execution successful.  
[14:10:09 INF] [] Handling request: /api/account/my-profile  
[14:10:09 INF] [] Handling request logProject: product  
[14:10:09 INF] [] Handling request logProjectGroupName: /ecs/product-dev-gateway  
[14:10:09 INF] [] Handling request logProject change tenant: product  
[14:10:09 INF] [Product] Executing endpoint '"Volo.Abp.Account.ProfileController.GetAsync (Volo.Abp.Account.Pro.Public.HttpApi)"'  
[14:10:09 INF] [Product] Route matched with "{area = \"account\", controller = \"Profile\", action = \"Get\", page = \"\"}". Executing controller action with signature "System.Threading.Tasks.Task`1[Volo.Abp.Account.ProfileDto] GetAsync()" on controller "Volo.Abp.Account.ProfileController" ("Volo.Abp.Account.Pro.Public.HttpApi").  
[14:10:09 INF] [Product] Executed action "Volo.Abp.Account.ProfileController.GetAsync (Volo.Abp.Account.Pro.Public.HttpApi)" in 13.5452ms  
[14:10:09 INF] [Product] Executed endpoint '"Volo.Abp.Account.ProfileController.GetAsync (Volo.Abp.Account.Pro.Public.HttpApi)"'  
[14:10:09 INF] [] Finished handling request.  
[14:10:09 INF] [] Request finished "HTTP/2" "GET" "https"://"localhost:44359""""/api/account/my-profile""" - 500 null "application/json" 195.4187ms  

Hi maliming,

I will check this one more time. Can we try a first approach, as it may work?

I have gone through the POC project, and after authenticating with the third-party IDP, we are redirected to the dashboard. After that, the following two API calls are automatically triggered from the Angular app to authenticate with our IDP:

https://localhost:44333/connect/authorize

1. https://localhost:44333/connect/authorize

2. 

However, when we apply the same process in our existing application, after the redirect to the dashboard, these two APIs are not being called automatically.

I have some question ?

1. This API not authenticated with our IDP that's why redirect to logout page right ?
2. As per my understanding above two screen shot API is base method API?
3. We override your login page done some custom changes that why not authorize first approach ?

For your reference i will share to you POC project as well as OIDC AUTH0 IDP server credentials. can you pls check and guide as per my understanding first approach it will work.

We need force fully call below method and authenticate with our IDP . https://localhost:44333/connect/authorize

please suggest .

suggest on this

ok

I have downloaded your project. Can you share the steps to reproduce the problem?

Thanks.

This is POC project not mine can you pls run your side able to redirect to dashboard..

hit below url in browser, it will make an API call to the SSO login endpoint.

http://localhost:4200?idp=oidc

Hi

shared pls check

POC project not able to shared you because browser restriction

The log does not contain the internal exception.

The logs of this 500 error should exist on the project, which depends on the AbpAccountPublicApplicationModule(Volo.Abp.Account.Pro.Public.Application) module.

[14:10:09 INF] [] Request starting "HTTP/2" "GET" "https"://"localhost:44359""""/api/account/my-profile""" - null null 
[14:10:09 INF] [] CORS policy execution successful. 
[14:10:09 INF] [] Handling request: /api/account/my-profile 
[14:10:09 INF] [] Handling request logProject: product 
[14:10:09 INF] [] Handling request logProjectGroupName: /ecs/product-dev-gateway 
[14:10:09 INF] [] Handling request logProject change tenant: product 
[14:10:09 INF] [Product] Executing endpoint '"Volo.Abp.Account.ProfileController.GetAsync (Volo.Abp.Account.Pro.Public.HttpApi)"' 
[14:10:09 INF] [Product] Route matched with "{area = \"account\", controller = \"Profile\", action = \"Get\", page = \"\"}". Executing controller action with signature "System.Threading.Tasks.Task`1[Volo.Abp.Account.ProfileDto] GetAsync()" on controller "Volo.Abp.Account.ProfileController" ("Volo.Abp.Account.Pro.Public.HttpApi"). 
[14:10:09 INF] [Product] Executed action "Volo.Abp.Account.ProfileController.GetAsync (Volo.Abp.Account.Pro.Public.HttpApi)" in 13.5452ms 
[14:10:09 INF] [Product] Executed endpoint '"Volo.Abp.Account.ProfileController.GetAsync (Volo.Abp.Account.Pro.Public.HttpApi)"' 
[14:10:09 INF] [] Finished handling request. 
[14:10:09 INF] [] Request finished "HTTP/2" "GET" "https"://"localhost:44359""""/api/account/my-profile""" - 500 null "application/json" 195.4187ms 

Hi maliming,

I will check this one more time. Can we try a first approach, as it may work?

I have gone through the POC project, and after authenticating with the third-party IDP, we are redirected to the dashboard. After that, the following two API calls are automatically triggered from the Angular app to authenticate with our IDP:

https://localhost:44333/connect/authorize

1. https://localhost:44333/connect/authorize

2. 

However, when we apply the same process in our existing application, after the redirect to the dashboard, these two APIs are not being called automatically.

I have some question ?

1. This API not authenticated with our IDP that's why redirect to logout page right ?
2. As per my understanding above two screen shot API is base method API?
3. We override your login page done some custom changes that why not authorize first approach ?

For your reference i will share to you POC project as well as OIDC AUTH0 IDP server credentials. can you pls check and guide as per my understanding first approach it will work.

We need force fully call below method and authenticate with our IDP . https://localhost:44333/connect/authorize

please suggest .

bwt, the question has too many replies.

Can you create a new question to reply?

Thanks

Hi ,

As per your request i have created new ticket.

https://abp.io/support/questions/8267/Tenant-Id-and-Tenant-Name-Not-Set-in-Header-After-Dashboard-Redirect-SSO-OIDC

Kindly please assign your self .

thanks

Tenant-Id and Tenant-Name Not Set in Header After Dashboard Redirect (SSO OIDC) #8132

https://abp.io/support/questions/8132/Tenant-Id-and-Tenant-Name-Not-Set-in-Header-After-Dashboard-Redirect-SSO-OIDC?CurrentPage=5