Histórico da Página

Provider
The provider options are: Google, Facebook, or LinkedIn (not generic), or generic (custom server).

Provider Name
Name to be displayed on the login screen.

If you add a non-generic provider, the following fields are required:

Application Identifier in Provider (ClientId)
ClientId is the provider identifier generated on Linkedin, Facebook, or Google.

Application Password in Provider (ClientSecret)
ClientId is the password generated by the provider itself.

Self-registration
Indicates Enter whether you can create the user at first login, or whether only users created via the Users menu will be able to authenticate.

If you add a generic provider provider, complete the following steps.

Application Identifier in Provider (ClientId)
ClientId is the provider identifier you want to use.

Application Password in Provider (ClientSecret)
ClientId is the password generated by the provider itself.

Self-registration
Indicates Enter whether you can create the user can be created at first login, or whether only users created via the Users menu will be able to authenticate.

Scopes
Scopes are routes that providers use, for example: e-mail address, username. Each provider has its own scope and usually documents this so that the user can consult it when registering.

Get User Information from ISP
When this option is checked, it always calls the provider's /me, even though it is OIDC.

Auth URL
Primary address to initiate authorization.

URI of token exchange with Provider (TokenURI)
It is the address to exchange the code for an access token (internally).

URI with Provider certificates (JWKS)
Certificate providing URI.

URI with user information by Provider
It's the /me address. Required when there is no such information coming from the IDToken (when the flow occurs through OAuth2 without OIDC).

URI with user's emaile-mail
This field is only required in a very specific case where when the email is not in the profile.

Provider parameter that contains the Token ID or Access Token 

Provider parameter with Access Token
If there is already a Token ID in the request and accessToken is still required for any call to the provider.

Variable with user name
Contained in the Token ID or /meresponse.

Variable with user's last name
Contained in the Token ID or /me response.

Variable with full user name
Contained in the Token ID or /me response.

Full name ID
If the Token ID or /me only contains the variable that contains the FullName, without the FirstName and LastName.

User emaile-mail
If the email e-mail is not contained in the Token ID or /me response.

After adding the new provider, the Identity login screen will present displays a button with the provider's name of the provider, so that allowing authentication with the user's account is allowed in the configured application.

A screen opens for file selection. The image must comply with the specifications displayed on the screen regarding the supported format (png) and the maximum size (1MB) specifications displayed onscreen. The image size is 50 x 50 pixels. If a logo is already defined for the provider, the corresponding image is displayed.

The target provider data will open so that you can query and edit the information can be consulted and changed.

For generic providers, the information to be changed is the same as the provider registration, according to Register provider item in this documentation.

For non-generic providers (Google, Facebook or Linkedin), you can only change the ClientId and ClientSecret can be changed.

When clicking this button, the link to access the provider is copied to the clipboard, so that the registration with the provider can be performed.

Click this button to copy the provider's access link to the clipboard and register it in the provider.

After deleting the provider, the button with the provider name will be is deleted from the Identity login screen.