improve auth capabilities for notification client and Swagger UI#304
Merged
improve auth capabilities for notification client and Swagger UI#304
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
add: notifications - Allow authentication via Client Credentials flow (breaking change)
change: make swagger docs compatible with access/authorization code flow
Why
We need to authenticate with client credentials in some scenarions.
Also
Implicitauth flow is deprecated and should not be used. So we need the Swagger UI with access/authorization code flow.References
ARTOSI-258
Checklist