PhenixID

Authenticators – internal – HeaderBased authentication

General information

This authenticator is used in a scenario where you have another security front end, such as a reverse proxy, that stands in front of PhenixID server. The front end server is also responsible of validating the user. The front end proxy needs to pass the username (or other attribute identifying the user) to the back end server (PhenixID server).

Modules required

auth-http

phenix-pipes

 

Configuration

Configuration Properties:

Name Description
successURL The URL to redirect the browser to after successful authentication. Mandatory.
pipeID Id of pipe to be executed for authenticator. Mandatory.
errorURL The URL to redirect the browser to if an error occurs.
header Name of the header containing the user identifier value

Example configuration

This example refers to a LDAP connection entity (local_ldap). This must be configured beforehand.

AUTHENTICATORS

{
“alias” : “header”,
“name” : “HeaderBasedAuthenticator”,
“configuration” : {
“pipeID” : “pipeValidateUserExists”,
“header” : “USERID”
},
“id” : “header”
}

 

 

PIPES

{

“id” : “pipeValidateUserExists”,

“valves” : [  {

“name” : “LDAPSearchValve”,

“config” : {

“connection_ref” : “local_ldap”,

“base_dn” : “o=IAMService”,

“scope” : “SUB”,

“size_limit” : 0,

“filter_template” : “(uid={{request.USERID}})”,

“attributes” : “”

}

}, {
“name” : “FlowFailValve”,

“config” : {

“message”:”User does not exist”,
“exec_if_expr” : “flow.items().isEmpty()”
}
}]

}

 

 

 


DISCLAIMER
Information provided in this document is for your information only. PhenixID makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners.

The origin of this information may be internal or external to PhenixID. PhenixID makes all reasonable efforts to verify this information.

PhenixID - support.phenixid.se