Create/Edit Partner Application

Use this page to add a partner application or to edit an existing one. Adding a partner application makes it accessible to the single sign-on server and enables users to log in to it using the single sign-on mechanism.

This page contains the following fields:

Partner Application Login

Field

Description

ID

(Displays only when editing a partner application)

The ID is automatically set when a partner application is added. It is used by the single sign-on server to identify the partner application.

Token

(Displays only when editing a partner application)

The token is automatically set when a partner application is added. It is used by the single sign-on server to identify the partner application.

The partner application must use the application token to identify itself to the single sign-on server when requesting authentication.

Encryption Key

(Displays only when editing a partner application)

The encryption key is automatically set when a partner application is added. When a user tries to log in, the single sign-on server generates a cookie that indicates a user's identity and whether the user has been authenticated. This key is used to encrypt the login cookie.

Name

Enter a unique name for the partner application.

Home URL

Enter the URL of the application home page.

Success URL

Enter the URL to the routine responsible for establishing the partner application session and session cookies. This routine should redirect the browser to the URL that the user originally requested.

The URL must point to a procedure that processes the user identification information from the single sign-on server. Include the http:// prefix in your URL. The following example shows a success URL for OracleAS Portal:

http://server.domain.com:5000/pls/DAD/portal.wwsec_app_priv.process_signon

Logout URL

Enter the URL for the logout routine of the application. The single sign-off page invokes this URL in parallel with others, enabling users to simultaneously log out of the server and active partner applications.

Field	Description
ID	(Displays only when editing a partner application) The ID is automatically set when a partner application is added. It is used by the single sign-on server to identify the partner application.
Token	(Displays only when editing a partner application) The token is automatically set when a partner application is added. It is used by the single sign-on server to identify the partner application. The partner application must use the application token to identify itself to the single sign-on server when requesting authentication.
Encryption Key	(Displays only when editing a partner application) The encryption key is automatically set when a partner application is added. When a user tries to log in, the single sign-on server generates a cookie that indicates a user's identity and whether the user has been authenticated. This key is used to encrypt the login cookie.
Name	Enter a unique name for the partner application.
Home URL	Enter the URL of the application home page.
Success URL	Enter the URL to the routine responsible for establishing the partner application session and session cookies. This routine should redirect the browser to the URL that the user originally requested. The URL must point to a procedure that processes the user identification information from the single sign-on server. Include the http:// prefix in your URL. The following example shows a success URL for OracleAS Portal: http://server.domain.com:5000/pls/DAD/portal.wwsec_app_priv.process_signon
Logout URL	Enter the URL for the logout routine of the application. The single sign-off page invokes this URL in parallel with others, enabling users to simultaneously log out of the server and active partner applications.

Valid Login Timeframe

Field

Description

Start Date

Enter the date when users will first be able to access the partner application through the single sign-on server. Use the format shown next to the field label.

End Date

Enter the end date when users are last able to access the partner application through the single sign-on server. If you leave this field blank, users are able to log in to the partner application indefinitely.

Field	Description
Start Date	Enter the date when users will first be able to access the partner application through the single sign-on server. Use the format shown next to the field label.
End Date	Enter the end date when users are last able to access the partner application through the single sign-on server. If you leave this field blank, users are able to log in to the partner application indefinitely.

Application Administrator

Field

Description

Administrator E-mail

Enter the e-mail address of the partner application administrator.

Administrator Information

Use this optional field to enter additional information about the partner application administrator.

Field	Description
Administrator E-mail	Enter the e-mail address of the partner application administrator.
Administrator Information	Use this optional field to enter additional information about the partner application administrator.