IdentityServer / IdentityServer4

OpenID Connect and OAuth 2.0 Framework for ASP.NET Core
https://identityserver.io
Apache License 2.0
9.23k stars 4.02k forks source link

Issuer in token have 2 different value #5450

Closed renus01 closed 2 years ago

renus01 commented 2 years ago

I am getting 2 different issuer in the token when i hit the same url of my app service. I have apigee and the backend azure app service with the runtime stack netcore2.1 Identityserver is integrated with default issueruri. we never overrides issueruri.

App service have the custom domain like xxxx.local.com and apigiee have the url like dev1-xxxx.com. The token endpoint dev1-xxxx.com/token which will generate the access/security token from idservice.

with the above config we are getting the indeterminate issuer in the generated token. one time dev1-xxxx.com (this is the apigiee url) and another time xxxx.local.com (this is the app service custom domain). what could be the issue in our code?

leastprivilege commented 2 years ago

Important update

This organization is not maintained anymore besides critical security bugfixes (if feasible). This organization will be archived when .NET Core 3.1 end of support is reached (3rd Dec 2022). All new development is happening in the new Duende Software organization.

The new Duende IdentityServer comes with a commercial license but is free for dev/testing/personal projects and companies or individuals making less than 1M USD gross annnual revenue. Please get in touch with us if you have any question.

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Questions are community supported only and the authors/maintainers may or may not have time to reply. If you or your company would like commercial support, please see here for more information.

github-actions[bot] commented 2 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.