Table of contents


Official Content

In GAMRemoteREST Authentication type (OAuth 2.0), you must consider following some configuration steps at both the GAM of the clients and at the Identity Provider.

Below is the client-side configuration.

Configure a GAMRemoteREST Authentication type.

SelectGAMRemoteREST

GAMRemoteRestClientConfig1

  • Function. Possible values are "Only Authentication" and "Authentication and roles". The latter means that user roles will be sent from the IDP to the client. The roles must be defined in the client as well as in the server, bearing in mind that the External Id has to be the same at the client and at the server. The criteria is the same as the one used in Managing Roles in applications using SSO.

  • Client Id and Client secret. The client Id and Client secret must be the same as the ones configured in the GAM Application at the server.

  • Version path. It indicates the version of the services to be called for solving the authentication. By default (if not set) it will be "v2.0". You may need to configure GAMRemoteREST authentication type against an Identity Provider of a previous version (prior to GeneXus 16 upgrade 7). In such case, set "v1.0" to this property, and the previous version - services (ServerUR/oauth/gam/accesstoken) will be called instead of the latest ($ServerURL/oauth/gam/v2.0/access_token).

  • Request these scopes. These scopes will be the user data requested to the IDP, if more scopes are requested than those shared by the IDP it will not be possible to authenticate. To know more details about them follow this link.

  • Additional scopes. Here you can detail more specifically which user scopes to request to the IDP. To know more details about them follow this link.

  • Remote Server authentication type name. Name of the authentication type in the IDP. By default it is the Default Authentication Type property of the IDP.

  • Remote server URL. Identity Provider's URL. It's the base URL, e.g: http://<server>/<Base_URL>

  • Private encryption key. The call among REST services may be encrypted. The same key must be configured in the IDP and in the client (this only works in v2.0 of the REST service implementation).

  • RepositoryGUID. Specifies the repository GUID in the IDP. It is necessary only if the IDP GAM is multitenant.

See Also

Server side configuration for GAMRemoteREST Authentication type


Last update: February 2024 | © GeneXus. All rights reserved. GeneXus Powered by Globant