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 JANUARY 02, 2024

Applies to:

Symptoms

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.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.