This repository has been archived by the owner on Mar 20, 2019. It is now read-only.
Check user active/passive from IPassiveable first on ProfileService. #61
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Check if the user is active from IPassiveable interface if entity implements it.
AspNetIdentity User entity has no active/passive property but on some scenario you need capability of making user active/passive.
This change depends on the IdentityServer/IdentityServer4.Storage#5 is merged and assumes a NuGet package published with a version number like "2.3.2" (version number can change, the current version for IdentityServer4.Storage is "2.3.1" so I choose the following number), else it won't build.