Jason Berk

we're fighting the same issue..... I noticed this: https://github.com/SparebankenVest/azure-key-vault-to-kubernetes/releases/tag/webhook-1.4.1 in the mean time, we pinned our image tag versions to `1.3.1` (as described by @MarkKharitonov) and testing seems to work

exact same issue with 5.2.1 today. I can't change the spec file, as it's provided by a vendor. Not sure what my options are.... EDIT: I switched to https://github.com/swagger-api/swagger-codegen/tree/master/modules/swagger-codegen-maven-plugin and...

I am also having issues using Okta spring boot v1.2.1 with boot 2.1.4.RELEASE. I have no `client-secret`. My UI is using PKCE and I have a client ID and issuer

Yes, this is what I'm doing and my resource server is still 401ing me. In my JS app I'm getting a token as I expected.... I just can't seem to...

> I'd suggest isolating the front end vs the backend. that's what I'm trying to do now.... > Can you access your resource server using curl/httpie? that's how I'm testing...

spring security debug logs show this error: Authentication request for failed: org.springframework.security.oauth2.core.OAuth2AuthenticationException: An error occurred while attempting to decode the Jwt: Couldn't retrieve remote JWK set: org.springframework.web.client.HttpClientErrorException$NotFound: 404 Not Found

I found this https://support.okta.com/help/s/article/Difference-Between-Okta-as-An-Authorization-Server-vs-Custom-Authorization-Server On Fri, May 22, 2020, 2:02 PM Brian Demers wrote: > Ahh, the issuer is the problem. This type of toke is from the root Okta...

I want my API (resource server) to only allow requests from callers that have an access token issued by okta specifically to users of my SPA. sounds like I need...

@bdemers can you help me with https://stackoverflow.com/questions/62227762/spring-security-filter-issues. It appears as if the filter created by the okta starter is being greedy