Single Sign-On (SSO) Account Locks When User Attempts To Run Financial Reporting (FR) Report Which References Members Of An Essbase Database To Which They Have No Access, And An Error Appears: "Connection could not be established "
(Doc ID 2209180.1)
Last updated on APRIL 17, 2018
Applies to:Hyperion BI+ - Version 18.104.22.168.000 and later
Information in this document applies to any platform.
You've configured EPM to use SSO via Microsoft Active Directory (MSAD). If a user runs an FR report that retrieves certain dimensions/members from an Essbase hierarchy, but they do not have access to those areas of the database, an error appears: "Connection could not be established ". This error occurs in conjunction with several attempts by the system to establish the ultimately unsuccessful connection, which results in the user's account getting locked out.
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