T Owens

The scope is accessible from the JWT. building upon https://github.com/okta/okta-jwt-verifier-golang#access-token-validation ``` jwt, err := jv.New().VerifyAccessToken(oktaToken) // get the scope iface := jwt.Claims["scp"] str := fmt.Sprintf("%v", iface) scope := strings.Trim(str, "[]")...

I would recommend the following vs. writing your own pkg. https://github.com/golang-jwt/jwt Combined with below depending on your needs. https://github.com/MicahParks/keyfunc

On an overlay: `thing/overlays/dev/kustomization.yaml` That looks like: ``` --- bases: - ../../base namespace: argocd resources: - applications/httpbin.yaml configMapGenerator: - name: argocd-cm behavior: merge literals: - url=https://argocd.thing.com ``` When running: `kustomize...

@Shell32-Natsu understood, thanks. The local kustomize version is ahead of what kubectl has. `kubectl -k` is pretty nice. Redirecting kustomize build isn't a deal breaker.