Siebel Portal Framework Guide > Integrating External Content > Understanding Portal Agents >

Server Redirect

The Server Redirect disposition type is no longer used in version 7.5, but is included in this guide for customers running prior versions of Siebel eBusiness applications.

In the Server Redirect scenario, the browser sends a request to Siebel Server. The Siebel Server sends the authentication request to the external application. After it receives a response from the external application, it creates a 302 Response, which contains the value of the target URL in the header. The Siebel Sever sends the 302 Response back to the browser and the browser is redirected to the target host.

Like Form Redirect, Portal Agents that use the Server Redirect disposition type should be configured to display the results in a new window rather than inline with other Siebel applets.

When using the Server Redirect disposition type, there is one required argument and several optional arguments. The arguments are defined below:

• SSO_REDIRECT_PATH. This is a required argument that defines the URL to which the browser is to be redirected. The value of this argument is sent as the URL in the header of the 302 Response.
• SSO_COOKIE_DOMAIN. This is an optional argument that specifies a domain for which the cookie is valid. If this argument is not defined, the domain of the external host (as defined in Host Administration view) is used.
• SSO_COOKIE_NAMES. This is an optional argument that allows you to define the cookies to be sent to the browser from the external application. If no cookie names are defined, the Portal Agent sends all cookies from the external site to client browser. For example, the argument defined in Table 4 specifies that only the cookies named Pid and tid are to be sent to the browser from the external host.

  Table 4.  Example Symbolic URL Argument

  Name	Argument Type	Argument Value
  SSO_COOKIE_NAME	Constant	Pid;tid

• SSO_COOKIE_PATH. This is an optional argument that allows you to define a subset of URLs to which the cookies apply.

You define these arguments in the Symbolic URL Argument applet. See Defining Symbolic URL Arguments for instructions on how to do this.