OIDCPostUidAndPassword
Warning
This authenticator is a legacy authenticator. It is recommended to plan for migrating the authenticator to the new protocol agnostic authenticator architecture. More information about the legacy authenticators can be found here.
Note
Used when authenticating using only username and password.
Properties
| Name | Description | Default value | Mandatory |
|---|---|---|---|
| pipeID | The id of the pipe validating username & passwor | N/A | Yes |
| loginTemplate | Name of the template file presenting the enduser UI entering credentials | login.template | No |
| userNameParamName | Parameter containing the username | username | No |
| passworParamterName | Parameter containing the password | password | No |
| useSessionManagement | Whether or not to return session_state | false | No |
Example Configuration
{
"alias": "oidcuidpwd",
"name": "OIDCPostUidAndPassword",
"configuration": {
"pipeID": "authPipe"
}
]
}
}
Configuring consent
To use consent, two parts needs to be configured. The authenticator in use and the authentication pipe.
Two consent parameters must be configured on the authenticator.
Secondly an additional valve, OIDCConsentDataValve, must be configured with the data the user will be asked to approve being sent. The format and available rules of the consent data can be found on the documentation page for the OIDCConsentDataValve.
Requirements
When using consent, a session must be available and the OIDCConsentDataValve must be placed before the SessionPersistValve in the pipe.
The data must be fetched prior to OIDCConsentDataValve with for example LDAPSearchValve.