Ueberauth Spotify Strategy v0.2.0 Ueberauth.Strategy.Spotify View Source

Spotify Strategy for Überauth.

Link to this section Summary

Functions

Includes the credentials from the Spotify response.

Provides the extra params for the user.

Handles the error callback from Spotify

The cleanup phase implementation for your strategy.

Handles initial redirect to the Spotify authentication page.

Fetches the fields to populate the info section of the Ueberauth.Auth struct.

Provides the uid for the user.

Link to this section Functions

Includes the credentials from the Spotify response.

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.

Handles the error callback from Spotify

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.

Handles initial redirect to the Spotify authentication page.

To customize the scope (permissions) that are requested by Spotify include them as part of your url:

"/auth/spotify?scope=user-read-email,user-read-privatet"

You can also include a state param that Spotify will return to you.

Fetches the fields to populate the info section of the Ueberauth.Auth struct.

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.