6.6 Authentication Flow

Figure 6-1 describes the authentication flow of OracleAS Single Sign-On support in Oracle Forms the first time the user requests an application URL that is protected by Oracle Application Server Single Sign-On:

Figure 6-1 Authentication Flow for First Time Client Request

1. The user requests a Forms URL similar to http(s)://<hostname>:<port>/forms/frmservlet?config=<application>&...

2. The Forms Servlet redirects the user to the OracleAS Single Sign-On server.

3. The user provides user name and password through Login form.

4. The password is verified through Oracle Internet Directory (LDAP Server).

5. The user gets redirected to the URL with sso_userid information.

6. Forms Servlet gets the database credentials from Oracle Internet Directory.

7. Forms Servlet sets the user ID parameter in the Runform session and the applet connects to the Forms Listener Servlet.

8. Forms Servlet starts the Forms Server.

Figure 6-2 describes the authentication flow of Oracle Application Server Single Sign-On support in OracleAS Forms Services when a user, authenticated through another Partner Application, requests an application that is protected by Oracle Application Server Single Sign-On.

Figure 6-2 Authentication Flow for Subsequent Client Requests

1. The user requests Forms URL.

2. Forms Servlet redirects the user to the OracleAS Single Sign-On Server.

3. The user gets redirected to the URL with sso_userid information.

4. Forms Servlet gets the database credentials from Oracle Internet Directory.

5. Forms Servlet sets the user ID parameter in the Runform session and the applet connects to the Forms Listener Servlet.

6. Forms Servlet starts the Forms Server.