This repository has been archived by the owner on May 22, 2021. It is now read-only.
Issue/14 #16
Open
Issue/14 #16
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
PAException
force-pushed
the
issue/14
branch
4 times, most recently
from
d913fc8
to
0383f4b
Compare
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.
The abstract class has to be implemented by any class and registers the
AuthenticationInterceptors.If you register a
AuthenticationServiceTokenInterceptorX-ServiceToken is checked on every route.sYou can add
@IgnoreServiceTokento a method, to avoid validatingX-ServiceToken.If you register a
AuthenticationScopeInterceptoryou can annotate routes/mehtods with@ Authenticationand they will be checked if the JWT is valid and if the user has the specific scope.You can use many of those annotations, every of them with the full scope.
Closes #14