GluuFederation / agama-openid

Agama Project to federate an external OpenID Connect Provider

Agama OpenID Connect Project

Use this project to delegate authentication to an external OpenID Connect provider (OP) using the authorization code flow.

How it works at a glance

When the main flow of this project is launched (namely, io.jans.inbound.openid) the user's browser is redirected to the authorization page of the configured OP. There authentication takes place and subsequently an access token is obtained to grab user profile data. A user entry is inserted in the local Jans database and a session is created for such "local" user in the Jans Authorization Server. Finally the user's browser is taken to the registered redirect URI.

Requirements

Enabled Agama

Ensure Agama is enabled in your Jans Server.

External OP settings

Obtain the following from the OP you want to support:

• The authorization endpoint URL
• The token endpoint URL
• The userinfo endpoint
• The scopes required to obtain user data
• Client credentials (client ID and secret)

In this process, you will be required to supplied a redirect URI, use the following: https://<jans-server-host-name>/jans-auth/fl/callback

Project deployment

• Copy (SCP/SFTP) the gama file of this project to a location in your Jans server
• Connect (SSH) to your Jans Server and open TUI: python3 /opt/jans/jans-cli/jans_cli_tui.py
• Navigate to the Agama tab and then select "Upload project". Choose the gama file
• Wait for about one minute and then select the row in the table corresponding to this project
• Press d and ensure there were not deployment errors
• Pres ESC to close the dialog

Project configuration

• Still with the row highlighted, press c and choose to export the sample configuration to a file
• Edit a copy of the file according to the OP settings formerly grabbed. They should go under the io.jans.inbound.openid section
• Still with the row highlighted, press c and choose to import configuration. Supply the file just edited

Testing

Configure the required in your Jans Server to be able to launch an authentication flow. Actual details may vary but you can resort to a handy browser extension called jans-tarp that will save you a good amount of work.

When testing ensure the following parameters are present in the authorization request:

• acr_values=agama
• agama_flow=io.jans.inbound.openid