Windows Native Authentication

How Windows Native Authentication Works The following steps, illustrated in Figure 8-1, describe what happens when a user tries to access a single-sign-on-protected application: 1. The user logs in to a Kerberos realm, or domain, on a Windows 2000 computer. 2. The user attempts to access a single-sign-on partner application using Internet Explorer. 3. The application redirects the user to the single sign-on server for authentication. As part of this redirection, the following occurs: a. The browser obtains a Kerberos session ticket from the Key Distribution Center (KDC). b. The single sign-on server verifies the Kerberos session ticket and returns the user to the requested URL. 4. The application provides content to the user. Configuring Windows Native Authentication for Oracle Application Server 10g (9.0.4) on Unix/Linux (Doc ID 264666.1) Configuring eBusiness Suite with Windows Native Authentication (WNA) (Doc ID 744118.1)