About Security and Authentication for Siebel Reports

It's recommended that you use the Siebel Security Model when configuring security and authentication for Siebel Reports. That model and a few others are discussed here.

Siebel Security Model

When Oracle Analytics Publisher receives a request from a Siebel user to perform report functionality on the server, it queries the Siebel application to retrieve the user privileges associated with that particular user. This retrieval is done by invoking a web service exposed by the Siebel application.

The Siebel Security model retrieves authentication information through the Siebel EAI Object Manager (EAIObjMgr) and, as a one-time event, authenticates sign-ins for report users against the Siebel database. After that, a session token is provided for Oracle Analytics Publisher authentication. Because every user executing reports has their own credentials and roles, users have private visibility on Oracle Analytics Publisher when scheduling reports.

Note: The reporting responsibilities in the Siebel application correspond to roles and permissions on Oracle Analytics Server (OAS). The names of these responsibilities must exactly match the corresponding set of roles on OAS.

LDAP

In an implementation using LDAP authentication, an LDAP security adapter provided with Siebel CRM authenticates users against an LDAP-compliant directory. The directory stores information that's required to allow users to connect to the database and Oracle Publisher Server and this information is retrieved by the security adapter when users try to run a report. When users sign in to a Siebel application that uses LDAP authentication, they're already authenticated for the current session.

Web Single Sign-On Authentication

This model lets you use a nonstandard security model, such as Siteminder or some other type of custom, single sign-on.

Oracle Analytics Publisher Security

When implementing Oracle Analytics Publisher security authentication for Siebel user access to the publisher server, all connections between the Siebel application and the publisher server are made using the same generic user account. This generic user account is useful for certain security topologies where multiple applications and authentication directories are used with a single shared Oracle Analytics Publisher instance.

Note: The Oracle Analytics Publisher security model doesn't enable private scheduled reports. All scheduled reports are considered public.

For more information, see the remaining topics in this chapter and the Oracle Analytics Publisher website.