-
Notifications
You must be signed in to change notification settings - Fork 15
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
Add Oauth2 support #114
Add Oauth2 support #114
Conversation
858d5be
to
dcad170
Compare
|
||
pa, passOK := content.Attributes["client_secret"] | ||
pv, _ := pa.Expr.Value(evalCtx) | ||
pass := seetie.ValueToString(pv) |
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.
Ich würde hier nicht von user
und pass
sprechen; die OAuth2-Nomenklatur ist client id und client secret. Also user
-> clientId
und pass
-> clientSecret
?
return "", "", "", fmt.Errorf("Missing OAuth2 'client_id' or 'client_secret' value") | ||
} | ||
|
||
key := oa.config.TokenEndpoint + "|" + user + "|" + pass |
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.
Ist der letzte Bestandteil des key
(also das client secret) nötig? Die client id ist pro authorization server eindeutig; client id und secret sind unveränderlich.
See #130 |
No description provided.