OBIEE 11g: Configuring Authentication and SSO with Active Directory and Windows Native Authentication
(Doc ID 1274953.1)
Last updated on AUGUST 13, 2019
Applies to:Business Intelligence Suite Enterprise Edition - Version 184.108.40.206.0  and later
Business Intelligence Reporting and Publishing Option - Version 220.127.116.11.0  and later
Business Intelligence Server Enterprise Edition - Version 18.104.22.168.0  and later
Information in this document applies to any platform.
This paper examines how to configure Oracle Business Intelligence Enterprise Edition (OBIEE) 11g to use Windows Server Active Directory (AD) as an LDAP Authentication source and how to use Windows Native Authentication (WNA) in an SSO environment.
The aim is to describe the configuration and set up required so that users may log on to their Windows PCs and access OBIEE via a standard web browser with no further authentication required on their part. Windows Native Authentication and Oracle Weblogic will be authenticating users to OBIEE using their standard network log ins without further troubling authorised users of the system.
There are several steps to be performed in Active Directory itself, in the Weblogic Server hosting OBIEE, in the OBIEE web app and finally on the client machine(s) from which you wish users to access OBIEE using Windows Native Authentication SSO.
The steps in this document have been tested with OBIEE version 22.214.171.124.0 and Active Directory 2008 (Windows Server 2008).
This document applies to all OBIEE 11.1.1.x versions.
Note that there are some additional steps to enable Smartview with this mechanism. These steps apply to Oracle BI 126.96.36.199.1 and later. These steps are documented in doc ID 1900485.1.
OBIEE Administrators. This requires in-depth knowledge of Windows Native Authentication /. Kerberos workings.
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