We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Implement a JWT backed authorizer: https://github.com/influxdata/influxdb/blob/master/authz.go#L19
This authorizer should be serializable as a JWT token to be used in communication with gateway. Much like how session works https://github.com/influxdata/influxdb/blob/master/session.go#L35.
Howevever, the token will contain a set of allowed permissions rather than describing the identity of author or owner.
Example scaffold:
package jwt import platform "github.com/influxdata/influxdb" var _ platform.Authorizer = (*Authorization)(nil) type Authorization struct{ Permissions []platform.Permission } func FromToken(token, secret string) (*Authorization, error) { // return deserialized authorization or JWT validation error } func (a *Authorization) ToToken(secret string) (string, error) { // serialize as JWT token string } // other required Authorizer methods
We can start work on adding support for this type of token in gateway.
The text was updated successfully, but these errors were encountered:
GeorgeMac
Successfully merging a pull request may close this issue.
Implement a JWT backed authorizer: https://github.com/influxdata/influxdb/blob/master/authz.go#L19
This authorizer should be serializable as a JWT token to be used in communication with gateway. Much like how session works https://github.com/influxdata/influxdb/blob/master/session.go#L35.
Howevever, the token will contain a set of allowed permissions rather than describing the identity of author or owner.
Example scaffold:
Success Criteria
We can start work on adding support for this type of token in gateway.
The text was updated successfully, but these errors were encountered: