Skip to content
This repository has been archived by the owner on Jul 31, 2024. It is now read-only.

Even after setting a Client Enabled to False it can still be used #2782

Closed
Robban1980 opened this issue Nov 7, 2018 · 3 comments
Closed

Comments

@Robban1980
Copy link

Using IdentityServer4 2.2, I can still request tokens with a client with Enabled set to False, with Resource Owner Password grant type. I tried to restart the server instance to make sure it was not a cache issue. But still the Enabled flag in the client store is not checked.

I found that there is an extension method that is used on the IClientStore to get active clients, that is used internally. But it seems this is not working with the EF store.

Issue / Steps to reproduce the problem

Configure IdentityServer to use configuration store through EF
.AddConfigurationStore(options =>
{
options.ConfigureDbContext = builder => builder.UseNpgsql(configurationConnectionStrinng, sql => sql.MigrationsAssembly(migrationsAssembly));
})

@Robban1980
Copy link
Author

could it have any link to this issue IdentityServer/IdentityServer3#3462

@Robban1980
Copy link
Author

Robban1980 commented Nov 7, 2018

Sorry about that, turns out I was messing up the DB update. No issue with IdentityServer. Please close this.

@lock
Copy link

lock bot commented Jan 12, 2020

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

@lock lock bot locked as resolved and limited conversation to collaborators Jan 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants