A non-authenticated user requests a resource protected by PingGateway or a Web Agent. Put the following events of the authentication lifecycle in…

The chronological order for a new user authentication flow is as follows:

1. The user attempts to access a protected resource (2).

2. The agent (PingGateway/Web Agent) intercepts the request and, finding no session, redirects the user to PingAM (5).

3. The user provides credentials by answering the authentication callbacks (1).

4. Upon success, PingAM creates a session and redirects the user back to the resource (6).

5. The agent validates the newly created session with PingAM (4).

6. Finally, the session lifecycle ends when it times out or the user logs out (3).

A. This sequence incorrectly suggests the user answers questions (1) before being redirected to the authentication service (5).

C. This sequence incorrectly places the session timeout (3) before the agent has a chance to validate the session (4).

D. This sequence incorrectly suggests the user answers questions (1) before being redirected to the authentication service (5).

1. Ping Identity, PingAM 7.3 Documentation, "Web Agents User Guide," Chapter: "How Web Agents Work," Section: "The Authentication Process". (Illustrates the redirect-based authentication flow).

2. Ping Identity, PingAM 7.3 Documentation, "PingGateway Guide," Chapter: "Protecting Applications and APIs," Section: "Protecting an Application". (Describes the interaction between the gateway, client, and PingAM).