Manual Chapter :
Configuring an Okta OAuth provider with discovery
Applies To:
Show Versions
BIG-IP APM
- 15.1.10, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0
Configuring an Okta OAuth provider with discovery
Configure the Okta OAuth server and make a note of the OpenID URI to use for discovery.
OAuth Discover uses the global system DNS
(not DNS resolvers) so you need to have configured a DNS remote lookup server using to use discovery.
You can configure an Okta OAuth provider to obtain opaque tokens or JSON web tokens (JWTs) from an OAuth authorization server that supports them. When an OAuth provider supports discovery from a well-known endpoint, APM can discover JWTs and JSON web key (JWK) configurations from the provider.
Without discovery, you can still create token and key
configurations in .
APM includes preconfigured providers named
AzureAD
(Azure Active Directory from Microsoft), F5
(APM), Facebook
, Google
, Okta
, and Ping
(PingFederate from Ping Identity).- On the Main tab, click .The Provider screen opens.
- ClickCreate.
- Type theNamefor the provider.
- From theTypefield, selectOkta.
- Select theTrusted Certificate Authorities.
- SelectUse Auto JWT.
- In theOpenID URIfield, specify the OpenID URI of the server.
- ClickDiscoverto fill in the remaining fields.This only works if you have configured a system DNS server in .
- ClickSave.The new Okta OAuth provider displays on the Provider screen.
