You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.
Hi So I have identityserber running on a computer(server) in a local network. So i can access the through the browser by either or . The problem is if i get the token with either, the issuer of the token become either the ip address or the computer name respectively. I realise that when using this setup to authenticate an API , the issuer is checked against the Authority I set in my Startup.cs for the .net core api application. According to the code in the documentation....
app.UseIdentityServerAuthentication(new IdentityServerAuthenticationOptions
{
Authority = "????",//How do i use multiple authorities
RequireHttpsMetadata = false,
ApiName = "api1"
});
How do i make sure the authority matches multiple names that refer to the same identity server
The text was updated successfully, but these errors were encountered:
I have a similar issue, but with a different scenario.
I have 1 IS in Kestrel which issues JWT tokens using the OpenID and the user-password scheme.
Another IS In IIS which issues JWT tokens using custom code which reads integrated windows authentication.
The problem is that if I add the two middlewares, one after the other, the authentication fails.
Hi So I have identityserber running on a computer(server) in a local network. So i can access the through the browser by either or . The problem is if i get the token with either, the issuer of the token become either the ip address or the computer name respectively. I realise that when using this setup to authenticate an API , the issuer is checked against the Authority I set in my Startup.cs for the .net core api application. According to the code in the documentation....
How do i make sure the authority matches multiple names that refer to the same identity server
The text was updated successfully, but these errors were encountered: