When trying to include RADIUS, Admin Console, or Office 365 applications in a newly created Authentication Policy, going to the Applications tab and clicking the Add App button does not show them as options.
- Okta Identity Engine (OIE)
- Authentication Policies
- Admin Console
- Office 365
- RADIUS Application
On OIE, RADIUS uses the legacy endpoint. Because of this, RADIUS needs to use different authentication policies than the rest of the applications. The same applies to applications such as Office 365 or the Admin console.
- For Office 365 and Admin Console applications, specific policies are in place that apply only to those applications.
- On the other hand, for the RADIUS App, the application needs to be selected first, and then a rule needs to be added to the Sign On Policy by going to the Sign On tab.
Why are certain policies not shareable?
While authentication policies can be shared across almost any OIDC or Okta Integration Network (OIN) app, policies for the Okta Admin Console, O365, and a few others cannot be shared with other apps. However, it is possible to continue utilizing the full power of the Okta Identity Engine and its capabilities for these apps. Also, when editing some policies (for example, RADIUS apps), Okta Classic experiences will still be observed as these policies have not been optimized for the Okta Identity Engine.
