Jason Parraga
> Currently there is not way to instrument `RedisReactiveCommands`. This should be added soon. I don't think these projects are supported any longer since OpenTelemetry is merging OpenTracing and OpenCensus
I've been seeing similar behavior where P50 for token validation is very low (sub ms) but the P99 for token validation is 5-10 seconds. I believe this has to do...
I ended up writing my own Okta JWT verifier with support for fetching OIDC metadata and JWK sets asynchronously in the background as to not block and slowdown the verification...
Just worked through this myself. ```go groups := []string{} groupIntfSlice, ok := jwt.Claims["groups"].([]interface{}) if !ok { // log } else { for _, groupIntf := range groupIntfSlice { group, ok...
Took a first shot at this and it is quite disruptive to many of the APIs and interfaces :/
Decided to roll my own verifier with support for open telemetry: https://github.com/Sovietaced/okta-jwt-verifier
Happy to file a pull request for this by the way.
> When this happens can you grab the JWT you are trying to validate? That should help narrow down the problem I can try to grab the JWT. We typically...
Filed a PR to fix this: https://github.com/okta/samples-golang/pull/126
I encountered 403s when I had issues with request signing. If the credentials are wrong the provider just blows up. So maybe there is an issue when you have username/password...