1. Reports Guide
  2. About Configuring Security and Authentication for Siebel Reports

About Configuring Security and Authentication for Siebel Reports

Depending on the kind of authentication you've set up, the application checks that a user exists in the directory as follows

  • For Siebel Security, checks by way of the endpoint that a user exists in the Siebel application.
  • For LDAP, checks for a user in the directory.
  • For Oracle Analytics Publisher security, there's no user directory check. The generic authentication credentials are checked against a user defined in Oracle Publisher. In this authentication model, responsibilities aren't checked. Instead, the same generic user account is used for the connection to Oracle Analytics Publisher Server.
    Note: For more information on Oracle Analytics Publisher Security, see Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher or Administering Oracle Analytics Publisher in Oracle Analytics Server.
  • Checks that a user has certain roles, depending on what action they're taking:
    • For LDAP, groups are created that relate to Oracle Analytics Publisher roles. Users in the LDAP directory have these certain groups assigned to them. Oracle Analytics Publisher authentication to LDAP directory checks for a user if they have a certain group.
    • For Siebel Security, each user has certain XMLP responsibilities. Oracle Analytics Publisher authentication to the Siebel application, by way of an endpoint inbound web service call, checks that a user has the correct responsibilities that relate to the Oracle Analytics Publisher roles.
  • Checks Siebel XMLP responsibilities that control the Siebel user interface for Reports menu restrictions (for example, XMLP_SCHEDULER responsibility for the scheduling option).