Publishing Reports to the Web - Downloads - Oracle

Configuring Out-of-the-Box OracleAS Single Sign-On
With OracleAS Single Sign-On, your administrator establishes a user identity for each
user. The administrator does this in the Oracle Internet Directory, through its user
interface, the Oracle Delegated Administration Services. You can access Oracle
Delegated Administration Services standalone or through OracleAS Portal. In either
case, the information is saved to the Oracle Internet Directory.
The user identity is comprised of the user name and password. Once users are
established, data source connection strings may be associated with them. At login,
users must enter their user names and passwords (their user identities), which will in
turn give them access to all of the data sources associated with those identities.
OracleAS Single Sign-On issues a session cookie that effectively acts as a key that
opens all authorized doorways for that session.
Note: For detailed information about the requirements and
procedures required for setting up SSO-related components, such
as the Oracle Internet Directory, see the Oracle Internet Directory
Administrator's Guide and the Oracle HTTP Server Administrator's
Guide on the Oracle Application Server documentation CD and on
the Oracle Technology Network, (http://otn.oracle.com).
10.2 Configuring Out-of-the-Box OracleAS Single Sign-On
By default, the Reports Server is secured and, to run a report, you must login with a
valid Single Sign-On userid and password. The Reports Server is configured by
default with the OracleAS Single Sign-On instance installed as part of Oracle
Application Server. The Oracle Internet Directory instance installed with Oracle
Application Server is used as the default repository for user and group information. If
you want to configure the Reports Server to use a different Oracle Internet Directory
instance or disable security, refer to Administering OracleAS Single Sign-On. For
information on how to add users to the Oracle Internet Directory, refer the Oracle
Internet Directory Administrator’s Guide. In addition, for each Oracle Application
Server installation, the Reports Server instances connect to the Oracle Internet
Directory as an application entity that is unique to the Oracle Application Server
installation. For more information on this behavior, refer to Connecting to the Oracle
Internet Directory.
If a user is not already logged in to OracleAS Single Sign-On, they are prompted to
login when they attempt to run a report to the Reports Server via rwservlet. If the
user parameters for a report include SSOCONN, OracleAS Single Sign-On will search
for the user’s data source credentials in the Oracle Internet Directory. If none are
found, then OracleAS Single Sign-On prompts the user to create a new resource. For
more information on rwservlet, refer to rwservlet. For more information about
SSOCONN, refer to SSOCONN.
The Reports Server is also configured to operate with OracleAS Portal by default. You
can optionally add reports to the portal and enable users to launch them from the
portal. Since users must login to the portal in this case, they are not prompted to login
again when they launch their reports because they have already been identified to
OracleAS Single Sign-On by logging in to the portal.
You can also optionally define access controls for resources associated with the Reports
Server (e.g., reports, printers, Reports Servers, and calendars) in OracleAS Portal. To
control access to resources, you must add them to the portal and specify their access
options. The resource access controls you specify in OracleAS Portal apply to reports
that you run outside of the portal as well. For example, if a user tries to run a report
10-2 Oracle Application Server Reports Services Publishing Reports to the Web