PBCS/ EPBCS: Enable Okta SSO Authentication
(Doc ID 2517129.1)
Last updated on NOVEMBER 02, 2019
Applies to:Oracle Planning and Budgeting Cloud Service - Version 17.01.25 and later
Information in this document applies to any platform.
Questions about enabling Okta authentication for PBCS Users.
1. Does Okta authentication also get enabled for smartview?
2. If there is a service account running integrations etc, What happens when we enable Okta authentication for that user?
3. When SSO fails, what is the backup to let the users bypass Okta and log in directly?
4. Is there a documentation from Oracle on enabling SSO on PBCS?
5. While logging into PBCS, we just log into one common domain before we can select the environment (Prod vs sandbox). How would SSO behave in such case? Is there a way to test SSO just on the sandbox before we deploy it in production?
6. I have a couple of provisioned users in PBCS with whose accounts we are running integrations. We are using EPMAutomate to run these jobs. Does that mean enabling SSO will cause is. sues for these jobs? I am not understanding how creating a native user will not have issues with SSO. For PBCS, there is no active directory authentication. So a native user will authenticate the same way as a regular user.Hello,
7. If EPMAutomate does not work, then what would be the workaround then? How to enable SSO without impacting their automations? Is there a way we can exclude our service account from SSO authentication so that it does not impact our EPMAutomate jobs?
8. How would logins from smartview be impacted once single sign on is enabled? would we need to maintain Hyperion credentials for smartview login? While logging through web, I understand that we will get authenticated via our SAML identity provider. But how does that work with smartview log ins?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document