identityserver3

.net core Client doesn't authenticate with IdentityServer v3 - Offset in Audience

孤街醉人 提交于 2020-01-24 09:43:00
问题 Given: IdentityServer v3 JavaSCript Client Asp Core Api Client The JavaScript client authenticates with the identityserver and makes a request with a bearer token to the api the api is configured to use ressource owner workflow Problem: Now I get: Audiences: 'http://localhost/identity/resources'. Did not match: validationParameters.ValidAudience: 'MyApi' or validationParameters.ValidAudiences: 'null' Obiviously Audiance doesn't match. what am I missing? Config ApiClient in Identity server:

.net core Client doesn't authenticate with IdentityServer v3 - Offset in Audience

丶灬走出姿态 提交于 2020-01-24 09:42:09
问题 Given: IdentityServer v3 JavaSCript Client Asp Core Api Client The JavaScript client authenticates with the identityserver and makes a request with a bearer token to the api the api is configured to use ressource owner workflow Problem: Now I get: Audiences: 'http://localhost/identity/resources'. Did not match: validationParameters.ValidAudience: 'MyApi' or validationParameters.ValidAudiences: 'null' Obiviously Audiance doesn't match. what am I missing? Config ApiClient in Identity server:

Refreshing claims without refreshing token

纵然是瞬间 提交于 2020-01-23 12:26:09
问题 We are using IdentityServer3 to authenticate our users. We run it on a separate web application to the main application API. There is a hierarchy of claims - for example, sites, factories and equipment. It is possible for a user to have a claim for a piece of equipment that is at a factory, but not have a claim for the entire factory, or the site. The distribution of claims is handled by means of a background job. When a user creates a site, factory or equipment a claim is created for them,

Secure IdentityManager with IdentityServer3

佐手、 提交于 2020-01-21 20:31:07
问题 In my setup I have IdentityManager on the same host of IdentityServer. All the required configuration is on database. To create my setup I have taken in consideration this question on stackoverflow.com and then followed all the regarding discussion on this github issue. I have also subscribed to Gitter to find the conversation mentioned on the SO question referenced. My setup is almost identical to the one of @ilter. However in my case I keep getting Error: You are not authorized to use this

Secure IdentityManager with IdentityServer3

泄露秘密 提交于 2020-01-21 20:29:46
问题 In my setup I have IdentityManager on the same host of IdentityServer. All the required configuration is on database. To create my setup I have taken in consideration this question on stackoverflow.com and then followed all the regarding discussion on this github issue. I have also subscribed to Gitter to find the conversation mentioned on the SO question referenced. My setup is almost identical to the one of @ilter. However in my case I keep getting Error: You are not authorized to use this

Oidc-client with IdentityServer3 - Angular2, how to logout and login properly

陌路散爱 提交于 2020-01-15 06:15:49
问题 Here's some background, I'm using implicit flow and my token is JWT. To logout, I'm using the method call signoutRedirectCallback. I want to be able to properly logout. So that I can login as a different user. When doing so, I still have the token from the last user? Is there a way to completely log the user out so that it doesn't have the last user's token? The token still persists for some reason. It seems that the only way to truly logout is when the browser page is closed and the cookie

Oidc-client with IdentityServer3 - Angular2, how to logout and login properly

帅比萌擦擦* 提交于 2020-01-15 06:12:50
问题 Here's some background, I'm using implicit flow and my token is JWT. To logout, I'm using the method call signoutRedirectCallback. I want to be able to properly logout. So that I can login as a different user. When doing so, I still have the token from the last user? Is there a way to completely log the user out so that it doesn't have the last user's token? The token still persists for some reason. It seems that the only way to truly logout is when the browser page is closed and the cookie

Identity server 4 token not validate in .NetFramework Api that use Identity Server 3

浪尽此生 提交于 2020-01-14 04:32:08
问题 In my identityserver app that use idsv4 and run on port "5000" have a client new Client { ClientId = "client", // no interactive user, use the clientid/secret for authentication AllowedGrantTypes = GrantTypes.ClientCredentials, // secret for authentication ClientSecrets = { new Secret("secret".Sha256()) }, // scopes that client has access to AllowedScopes = { "api1" } }` and in my .Net Framework Api's startup class that use port no "7001" : app.UseIdentityServerBearerTokenAuthentication( new

Thinktecture identity server client selection and implementation

有些话、适合烂在心里 提交于 2020-01-14 03:15:39
问题 I am trying to get my head out of the clouds with identity server. I would like to implement the identity server project to let authenticate An ASP.NET MVC 5 application An ASP.NET Web API A windows service implementation Int this blog post I have read some details about clients. The author simply state: OAuth 2 provides several "grant types" for different use cases. The grant types defined are: Authorization Code for apps running on a web server Implicit for browser-based or mobile apps

Getting Scopes and Clients from Database instead of InMemoryClients & InMemoryScopes Identity Server 3

可紊 提交于 2020-01-04 01:06:20
问题 I want to read Scopes and Clients from database instead of InMemoryClients & InMemoryScopes in Identity Server 3. Any one please help me how to read how we can achieve this in identity server 3. Thanks in advance. 回答1: From the docs (https://identityserver.github.io/Documentation/docsv2/ef/overview.html): If scope or client data is desired to be loaded from a database (rather than use in-memory configuration), then we provide a Entity Framework based implementations of the IClientStore and