Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get paged list of users with UserManager. #22597

Closed
mikeandersun opened this issue Jun 5, 2020 · 3 comments
Closed

Get paged list of users with UserManager. #22597

mikeandersun opened this issue Jun 5, 2020 · 3 comments
Labels
area-identity Includes: Identity and providers Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update.

Comments

@mikeandersun
Copy link

How I can get paged list of users just with UserManager not direct access to IdentityDbContext?
I think it is better to have some APIs to get users?

@blowdart blowdart added the area-identity Includes: Identity and providers label Jun 5, 2020
@blowdart
Copy link
Contributor

blowdart commented Jun 5, 2020

Via dbcontext is the best way to do it. The identity stores are meant for login and updating, not the sort of operations that would produce a list.

We are not considering this sort of feature at this time.

@blowdart blowdart added the Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. label Jun 5, 2020
@mikeandersun
Copy link
Author

I think UserManager can be out of Identity with some abstraction APIs to CRUD action on users.
I needs to use UserManager without SignInManager for users management . I'm unhappy to use unrelated code in my application.

@ghost ghost added Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. and removed Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. labels Jun 9, 2020
@blowdart
Copy link
Contributor

Unfortunately that's just the way it's designed, and we currently have no plans to further separate things.

Closing as by design.

@ghost ghost locked as resolved and limited conversation to collaborators Jul 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-identity Includes: Identity and providers Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update.
Projects
None yet
Development

No branches or pull requests

2 participants