ueberauth_bungie v0.1.0 Ueberauth.Strategy.Bungie View Source

Bungie Strategy for Ueberauth

Link to this section Summary

Functions

Provides the credentials for the user

Provides the extra params for the user

Cleans up the private area of the connection used for passing the raw Gitlab response around during the callback

The request phase implementation for your strategy

Provides the info for the user

Provides the uid for the user

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.

Provides the extra params 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 extra key.

You would include any additional information within extra that does not fit in either info or credentials

Callback implementation for Ueberauth.Strategy.extra/1.

Cleans up the private area of the connection used for passing the raw Gitlab response around during the callback.

The request phase implementation for your strategy.

Setup, redirect or otherwise in here. This is an information gathering phase and should provide the end user with a way to provide the information required for your application to authenticate them.

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

Provides the info 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 info key.

Callback implementation for Ueberauth.Strategy.info/1.

Provides the uid 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 uid key.

Callback implementation for Ueberauth.Strategy.uid/1.