Added configuration from json file #231
Merged
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
added 6 commits
March 27, 2019 14:29
|
Great work, I will test it. 👍 |
added 5 commits
April 17, 2019 22:07
…oruba/IdentityServer4.Admin into seeding-db-with-json-document
…oruba/IdentityServer4.Admin into seeding-db-with-json-document
…oruba/IdentityServer4.Admin into seeding-db-with-json-document
|
I'll add additional code for deserializing System.Security.Claims from Json, because by default they have trouble with that. So do not pull this just yet. |
…rs naming convention;
…ataConfiguration to IdentityServerDataConfiguration
skoruba
approved these changes
Oct 5, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Configuration read from json file. What do you think? I'd like to remove hardcoded code in the next commit :)
Client secrets are hashed before being pumped into db.