-
Notifications
You must be signed in to change notification settings - Fork 36
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
Authn chain elements #154
Authn chain elements #154
Conversation
Signed-off-by: Ilya Lobkov <ilya.lobkov@xored.com>
Signed-off-by: Ilya Lobkov <ilya.lobkov@xored.com>
Signed-off-by: Ilya Lobkov <ilya.lobkov@xored.com>
Signed-off-by: Ilya Lobkov <ilya.lobkov@xored.com>
Signed-off-by: Ilya Lobkov <ilya.lobkov@xored.com>
@edwarnicke I think this PR can be useful for Advanced OPA Policies. Can you please take a look? |
} | ||
|
||
token := request.GetConnection().GetPath().GetPathSegments()[request.GetConnection().GetPath().GetIndex()].GetToken() | ||
if err := security.VerifyToken(token, x509crt); err != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we do the token verification in OPA?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is a good idea, will do :)
Depends on #152
Description
Add 2 chain elements:
AuthnClient
adds token to the currentPathSegment
(pointed byIndex
)AuthnServer
verifies token of the currentPathSegment