This repo is home to the Gluu Agama-PW project. This Agama project provides standard username-password authentication for a person.
The project can be deployed to any IAM server that runs an implementation of the Agama Framework like Janssen Server and Gluu Flex.
Different IAM servers may provide different methods and user interfaces from where an Agama project can be deployed on that server. The steps below show how the Agama-PW project can be deployed on the Janssen Server.
Deployment of an Agama project involves three steps
- Downloading the
.gamapackage from project repository - Adding the
.gamapackage to the IAM server - Configure the project
Tip
Skip this step if you use the Janssen Server TUI tool to
configure this project. The TUI tool enables the download and adding of this
project directly from the tool, as part of the community projects listing.
The project is bundled as
.gama package.
Visit the Assets section of the
Releases to download
the .gama package.
The Janssen Server provides multiple ways an Agama project can be deployed and configured. Either use the command-line tool, REST API, or a TUI (text-based UI). Refer to Agama project configuration page in the Janssen Server documentation for more details.
Agama project accepts configuration parameters in the JSON format. Every Agama project comes with a basic sample configuration file for reference.
Below is a typical configuration of the Agama-PW project. As show, it contains configuration parameters for the flows contained in it:
{
"org.gluu.agama.pw.main": {
"MAX_LOGIN_ATTEMPT": "6",
"ENABLE_LOCK": "true",
"LOCK_EXP_TIME": "180"
}
}
Check the flow detail section for details about configuration parameters.
Use any Relying party implementation (like jans-tarp) to send authentication request that triggers the flow.
From the incoming authentication request, the Janssen Server reads the ACR
parameter value to identify which authentication method should be used.
To invoke the org.gluu.agama.pw.main flow contained in the Agama-PW project,
specify the ACR value as agama_<qualified-name-of-the-top-level-flow>,
i.e agama_org.gluu.agama.pw.main.
Fork this repo to start customizing the Agama-PW project. It is possible to customize the user interface provided by the flow to suit your organization's branding guidelines. Or customize the overall flow behavior. Follow the best practices and steps listed here to achieve these customizations in the best possible way. This project can be re-used in other Agama projects to create more complex authentication journeys. To re-use, trigger the org.gluu.agama.pw.main flow from other Agama projects.
To make it easier to visualize and customize the Agama Project, use Agama Lab.
List of the flows:
org.gluu.agama.pw.main flow represents single step username and password authentication. This flow allows a configurable number of incorrect login attempts along with the ability to call account locking endpoint if the attempts reach the maximum allowed number.
sequenceDiagram
title Agama-PW Basic Flow
actor Person
participant Browser
participant website
participant IDP
participant Authenticate
Person->>IDP: Sign-in request
IDP->>Browser: uid/pw Form
Person->>Browser: Creds
Browser->>IDP: POST Form
IDP->>Authenticate: validate(uid, pw)
Authenticate->>IDP: {"result":"success","code": 200,"message": "OK"}
IDP->>Browser: OpenID Code
Browser->>website: callback
- MAX_LOGIN_ATTEMPT: Is the maximum failed login attempt before the user account is locked
- ENABLE_LOCK: true/false, enables or disables the Account Lock feature
- LOCK_EXP_TIME: The time in seconds before a locked account is unlocked.
Check out this video to see the agama-pw authentication flow in action. Also check the Agama Project Of The Week video series for a quick demo on this flow.
Note: While video shows how the flow works overall, it may be dated. Do check the Test The Flow section to understand the current method of passing the ACR parameter when invoking the flow.