You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
a, err:=h.AuthorizationService.FindAuthorizationByToken(ctx, t)
iferr!=nil {
returnctx, err
}
returnplatcontext.SetAuthorizer(ctx, a), nil
}
If an error is returned because it is not a well formed token or no JWT secret exists then attempt to find authorization using the token as we currently do so.
If an error is returned because the token is well-formed, however, it is invalid (invalid signature, expired and so on) then return the error.
If the token is valid and the permissions can be deserialized then set the authorizer on the context.
Success Criteria
When configured with a JWT secret, API actions can be triggered using a well formed token. e.g. a token with permissions with write action for a specific bucket within a specific org can be generated using a secret and then used to trigger a write.
The text was updated successfully, but these errors were encountered:
Add support for deserialization / validation of JWT based authorizer within authentication middleware:
https://github.com/influxdata/influxdb/blob/master/http/authentication_middleware.go
Steps:
influxdb/http/authentication_middleware.go
Lines 104 to 116 in feda6dc
Success Criteria
When configured with a JWT secret, API actions can be triggered using a well formed token. e.g. a token with permissions with write action for a specific bucket within a specific org can be generated using a secret and then used to trigger a write.
The text was updated successfully, but these errors were encountered: