Exposing the current version of Okta's Open API Spec via a .well-known endpoint would allow API consumers to fetch and cache this at runtime
Okta has a lot of prior art using .well-known endpoints for use cases outside Oauth2 e.g .well-known/okta-organization
Exposing the Spec at an API endpoint could also potentially fix #225 and #227
Exposing the current version of Okta's Open API Spec via a
.well-knownendpoint would allow API consumers to fetch and cache this at runtimeOkta has a lot of prior art using
.well-knownendpoints for use cases outside Oauth2 e.g.well-known/okta-organizationExposing the Spec at an API endpoint could also potentially fix #225 and #227