Ueberauth OpenAM strategy v0.2.0 Ueberauth.Strategy.OpenAM View Source

OpenAM Strategy for Überauth. Redirects the user to an OpenAM login page and verifies the auth token the OpenAM server returns after a successful login. The login flow looks like this:

  1. User is redirected to the OpenAM server's login page by Ueberauth.Strategy.OpenAM.handle_request!
  2. User signs in to the OpenAM server.
  3. OpenAM server redirects back to the Elixir application, sending an auth token as an HTTP Cookie header.
  4. This auth token is validated by this Überauth OpenAM strategy, fetching the user's information at the same time.
  5. User can proceed to use the Elixir application.

Link to this section Summary

Functions

Provides the credentials for the user

Ueberauth extra information callback. Returns all attributes the OpenAM server returned about the user that authenticated

Ueberauth after login callback with a valid OpenAM Cookie

The cleanup phase implementation for your strategy

Ueberauth request handler. Redirects to the OpenAM server's login page

Ueberauth user information

Ueberauth UID callback

Link to this section Functions

Provides the credentials for the user.

This is one of the component functions that is used to construct the auth struct. What you return here will be in the auth struct at the credentials key.

Callback implementation for Ueberauth.Strategy.credentials/1.

Ueberauth extra information callback. Returns all attributes the OpenAM server returned about the user that authenticated.

Ueberauth after login callback with a valid OpenAM Cookie.

The cleanup phase implementation for your strategy.

The cleanup phase runs after the callback phase and is present to provide a mechanism to cleanup any temporary data your strategy may have placed in the connection.

Callback implementation for Ueberauth.Strategy.handle_cleanup!/1.

Ueberauth request handler. Redirects to the OpenAM server's login page.

Ueberauth user information.

Ueberauth UID callback.