
vll3h (vll3h) asked a question.
Hi,
We have created an application in Okta to use OpenID Connect and we're following the documentation at https://developer.okta.com/docs/guides/sign-into-web-app/springboot/before-you-begin/. The instructions say to add this to our Spring Boot application properties:
okta.oauth2.issuer=https://${yourOktaDomain}/oauth2/default
The value looks like it relates to the default custom Authorization Server when using API Access Management, which we aren't. The value causes our application to not start and the error says that the issuer URL is not accessible.
I can fix the problem by changing the issuer value to https://${yourOktaDomain} but this results in a 404 response during the Authorization Code flow as the Okta Spring Boot SDK redirects to https://${yourOktaDomain}/v1/authorize. Our OIDC metadata at https://${yourOktaDomain}/.well-known/openid-configuration lists the authorization_endpoint as https://${yourOktaDomain}/oauth2/v1/authorize.
We are using v1.4.0 of the Okta Spring Boot SDK, would it help if we upgrade to v2.0.1, or is there a different problem here?
Regards, Ben

Hey Ben!
Looks like you may have already found this, but I'm going to link back to the Github Issue where our Java SDK engineers have confirmed that support for the Org Authorization Server has been added to the latest version of the Spring Boot Starter
https://github.com/okta/okta-spring-boot/issues/273