Starts in:
1 DAY
1 HR
16 MIN
2 SEC
Starts in:
1 D
1 H
16 M
2 S

Activities of "NH-Support"

Hi

Changing the audience didn't make any difference.

Just to keep in mind this application is in production and it is operating well using the IIS web server.

This issue is related to the Kubernetes deployment where we need to add another endpoint to auth-server in order to communicate with it within the internal cluster, so the metadata address is the http://<k8s service name> and the authority is https://<the external domain name> when metadata address is added to the code the errors in ticket start to appear, while if we stick with the authority URL only it will not be reachable from inside the cluster.

I hope that this will clarify the situation we have.

Hi, Kindly find below the PreConfigureServices in the AuthServerModule

Kindly note that the URLs are only accessible from our local environment.

Let me know if you still need the URLs, I will share it with you if it is still needed

Hi Anjali

actually, we don't have PreConfigureService

but this is ConfigureService if you want to check

and this is the configure authentication for adding the metadata URL

and from Swagger, i can execute any API with a 200 status code

but when we log in from the angular app it throws the following error

It requests the jwks from HTTPS while it is the auth-server is operating on HTTP in the local environment

requirehttpsmetadata is false in the angular environment.json, backend, and auth-server appsettings.json

this is where we reach tell now.

I hope that you can help us fix this issue.

thank you,

can you provide the logs of the HTTP500 error

the requested API is returning HTTP 500 because it requires authentication and when it tries to authenticate it throws this error unable to obtain ..... However, the API now can authenticate but the angular can't while it is trying to fetch from https://auth-server/.well-known/jwks it is not specified to use HTTPS so it returns connection refused

Please find the code section for adding metadata URL

Please advise.

thank you,

When i try to execute an API from Swagger i am getting the error attached in the image

While if i do Curl from inside the backend pod the same URL http://hub-authserver.hub-qa it will response successfully

can you please advice

Hello nanohealthserviceaccount,

Please do let us know if this solution has worked for you?

Awaiting for your response.

Thank You, Anjali

is it possible to get a live support session ? as this is holding us back and we need to do ASAP

Hello nanohealthserviceaccount,

Could you please check below link

https://github.com/abpframework/abp/issues/6247#issuecomment-778150542

Please do let me know if it helps you or if anything else is needed.

Thank you, Anjali

Hi Anjali

The solution you provided is already implemented in my code and i am still having the same issue

could you please suggest any other solution for this ?

Hello nanohealthserviceaccount,

Could you please share your appsettings.json file from AuthServer and environment.ts file from Angular so that we can help you better.

Thank you, Anjali

Hi Please check the attached pictures

this is environment.json

this is appsettings.json for backedn

this is appsettings.json for auth-server

Hi,

I have a Front-end Application that use Angular as framework, I have Auth Server [OpenIDDICT] and Backend API [ASP.NET]

When i try to open https://myfront.domain.local and Click Login ====> it will take me to the Auth Server ======> After entering the username and password it will redirect me again to the Front-end

i attached a screenshot for the logs

  1. the swagger is running fine and it can do authorization from the swagger api interface
  2. the auth server is running fine and i can login without issues (if i opened it directly from the web)
  3. if i opened the front then tried to login with valid creds it redirecting me to front-end page again and logs the error showed in the attached picture

Showing 21 to 30 of 32 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06