01.02.2013 Views

Publishing Reports to the Web - Downloads - Oracle

Publishing Reports to the Web - Downloads - Oracle

Publishing Reports to the Web - Downloads - Oracle

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

About <strong>Oracle</strong>AS <strong>Reports</strong> Services Security<br />

Figure 9–1 <strong>Oracle</strong> Delegated Administration Services Create Resource<br />

6. rwservlet constructs a command line from <strong>the</strong> URL (and <strong>Oracle</strong> Internet<br />

Direc<strong>to</strong>ry information if you used SSOCONN) and passes it <strong>to</strong> <strong>the</strong> <strong>Reports</strong> Server.<br />

7. The <strong>Reports</strong> Server validates <strong>the</strong> user credentials against <strong>the</strong> <strong>Oracle</strong> Internet<br />

Direc<strong>to</strong>ry server. The <strong>Reports</strong> Server checks whe<strong>the</strong>r <strong>the</strong> user has <strong>the</strong> necessary<br />

privileges <strong>to</strong> run <strong>the</strong> report on <strong>the</strong> specified server at <strong>the</strong> specified time <strong>to</strong> <strong>the</strong><br />

specified destination. If <strong>the</strong> validation check fails for any reason, <strong>the</strong>n an error<br />

condition is returned <strong>to</strong> <strong>the</strong> user and <strong>the</strong> process terminates.<br />

8. The <strong>Reports</strong> Server delegates <strong>the</strong> job <strong>to</strong> a <strong>Reports</strong> Engine that accesses <strong>the</strong> data<br />

source, retrieves <strong>the</strong> data, and formats <strong>the</strong> report.<br />

9. The completed output is sent <strong>to</strong> <strong>the</strong> specified destination. Depending upon <strong>the</strong><br />

destination, <strong>the</strong> output may be sent <strong>to</strong> a printer, served back <strong>to</strong> <strong>the</strong> browser, or<br />

s<strong>to</strong>red in a file for future reference.<br />

9.1.2.2 Handling Report Requests without <strong>Oracle</strong>AS Single Sign-On<br />

If Single Sign-On is not being used, <strong>the</strong>n any user accessing a secured instance of <strong>the</strong><br />

<strong>Reports</strong> Server is challenged <strong>to</strong> identify <strong>the</strong>mselves by rwservlet via its own<br />

au<strong>the</strong>ntication mechanism (identical <strong>to</strong> <strong>the</strong> behavior of <strong>Oracle</strong> <strong>Reports</strong>6i). Because <strong>the</strong><br />

HTTP 1.0 pro<strong>to</strong>col is stateless (i.e., each call <strong>to</strong> <strong>the</strong> server is effectively independent of<br />

all o<strong>the</strong>rs), users might need <strong>to</strong> au<strong>the</strong>nticate <strong>the</strong>mselves for each report request unless<br />

a cookie is maintained. To allow users <strong>to</strong> au<strong>the</strong>nticate <strong>the</strong>mselves only once per<br />

session, rwservlet has its own client-side cookie, <strong>the</strong> authid cookie, in which it s<strong>to</strong>res<br />

<strong>the</strong> required au<strong>the</strong>ntication information for <strong>the</strong> current session. Once <strong>the</strong> user is<br />

au<strong>the</strong>nticated, an encrypted cookie is created in <strong>the</strong> browser <strong>to</strong> enable <strong>the</strong> user <strong>to</strong><br />

submit multiple report jobs without re-au<strong>the</strong>nticating for each request.<br />

Note: If you want <strong>to</strong> force users <strong>to</strong> au<strong>the</strong>nticate <strong>the</strong>mselves for a<br />

specific report, you can use <strong>the</strong> SHOWAUTH command line option.<br />

Alternatively, you can include a %S in <strong>the</strong> corresponding report<br />

entry in <strong>the</strong> key map file. This file is usually called cgicmd.dat<br />

and is located in ORACLE_HOME\reports\conf. %S forces users<br />

<strong>to</strong> enter <strong>the</strong>ir username and password each time <strong>the</strong> report is called.<br />

Securing <strong>Oracle</strong>AS <strong>Reports</strong> Services 9-5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!