Example that doesn't assume use of a developer account

[zachgrayio]

I've noticed that pretty much all of the samples make the assumption of an Okta developer account; this really isn't useful when trying to work out how to provide Okta SSO support to a web app that actual Okta users will consume, as real enterprise Okta accounts don't have the default authentication server available.

It would be great if the docs described how to connect to real Okta deployments, as this information is hard to come by

[whod81]

Seconded.

[monde]

@zachgrayio , @whod81 , thanks for the feedback and I agree. We've been discussing the need to document account and feature flag assumptions.

[zachgrayio]

I think also an example of using okta for simple sso is entirely missing here. The current examples are assuming that okta acts as the authorization server using either the dev account or an upgraded okta license and validates the JWT against that api etc. IIRC our backend devs just ended up deleting most of the code shown here in the end as some of it was redundant for our simple use case