Activities of "Repunjay_TASC"

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

hi

Request starting "HTTP/2" "GET" "https"://"localhost:44359""""/api/account/my-profile""" - null null

https://localhost:44359/api/account/my-profile is just forwarding the request, it is not the real API.
When you see the 500 error, please check the logs of the real API to see the reason.

The current logs are from 1️⃣ or 2️⃣, Check the logs of 3️⃣ (microservice)

If you are unsure, please delete all websites' logs.txt files, reproduce the problem, and share all logs.txt files.

Thanks

Hi , I know it's forward api and it's base method not able to debug as well what ever logs store in log.txt file i shared with you.

hi

Please share a screenshot of your solution structure.

front-end, we’re using Angular, while on the back-end, we’re using microservices. At the database level, we’re using pgAdmin.

I’ve also shared an email with a high-level structure screenshot and the OIDC code that I used on the Angular side. Please review it and let me know your thoughts.

This issue is escalating internally and is creating a bad impression with the client. I’ve been trying to convince the team to set up a call and resolve this. I completed the POC, and it works as expected, but we’re still facing issues with the actual implementation in the project, and the problem remains unresolved.

With this communication, I’m unsure when we will resolve this issue.

As I mentioned earlier, we have an old template with the updated version. Once you review the code, you’ll definitely be able to understand it and resolve the issue. For your information, the modifications we made earlier were done with the support of your team during the call.

Yes i am calling gateway api .

this is base method right ?

below API i have call from angular and token pass which is coming from 3rd party IDP.

Which token need to pass this api ? ABP or 3rd party IDP. ?

???

Yes i am calling gateway api .

this is base method right ?

below API i have call from angular and token pass which is coming from 3rd party IDP.

Which token need to pass this api ? ABP or 3rd party IDP. ?

Hi ,

shared latest log information pls check and let me know.

shared logs over email please check