Provide support for custom authorization servers in Okta

Created on 29 February 2024, about 1 year ago
Updated 2 April 2024, about 1 year ago

Problem/Motivation

Okta has two types of authorization servers: the org authorization server and the custom authorization server.

In order to access various claims it may be necessary to use a custom authorization server, but the OpenIDConnectOktaClient plugin hardcodes the endpoints to use the org authorization server.

Steps to reproduce

Proposed resolution

  • Provide option to use either:
    • the org authorization server,
    • the default custom authorization server, or
    • a user-created custom authorization server
  • If default custom authorization server is selected, inject /default/ in the endpoint URLs, e.g. /oauth2/default/v1/authorize
  • If custom authorization server is selected, allow the user to specify the authorization server id and inject it in the endpoint URLs, e.g. /oauth2/aus9o8wzkhckw9TLa0h7z/v1/authorize
  • Provide a link to https://developer.okta.com/docs/concepts/auth-servers/ on the Okta plugin configuration form

Remaining tasks

User interface changes

API changes

Data model changes

Feature request
Status

Needs work

Version

3.0

Component

Code

Created by

🇦🇺Australia mstrelan

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024