• Log in to BI Publisher as an administrator.
  • Click on the Admin tab.
  • Click on Security Configuration.
  • For Security Model, choose LDAP and enter the following parameters:
    SettingExample Value
    URLldap://ad.mycompany.com:389 Your company’s LDAP server and port.
    Administrator UsernameCN=ADMIN,OU=Users,OU=Shared Services,DC=mycompany,DC=com The fully qualified DN of the account you use to sign in to LDAP.
    Administrator Passwordmyxlplyx The password for the above account.
    Distinguished Name for UsersDC=mycompany,DC=com The “root” level at which to search for users.
    Distinguished Name for GroupsOU=Global Groups,DC=mycompany,DC=com The “root” level at which to search from groups.
    Group Search Filter(&(objectClass=group)(
    Group Attribute Namecn
    Group Member Attribute Namemember
    Member Of Group Attribute Name
    Group Description Attribute Namedescription
    JNDI Context Factory Classcom.sun.jndi.ldap.LdapCtxFactory
    Group Retrieval Page Size
    attribute used for RDNsAMAccountName Allows users to log in to BI Publisher using their corporate AD account name.
    Automatically clear LDAP cacheChecked
    Ldap Cache Interval1
    Ldap Cache Interval UnitHour
    Default User Group Name
    Attribute Names for Data Query Bind Variables

  • Bounce BI Publisher.
  • Try logging in with your corporate AD credentials. Remember, you need to be assigned to one of the following special groups in Active Directory if you want developer or admin privileges in BI Publisher:

XMLP_ADMIN
XMLP_DEVELOPER
XMLP_SCHEDULER
XMLP_ANALYZER_EXCEL
XMLP_ANALYZER_ONLINE
XMLP_TEMPLATE_DESIGNER

You can read more about those roles and what they do in the Oracle Documentation.