Glewlwyd HTTP Basic Authentication Schema documentation

Single Sign On server, OAuth2, Openid Connect, multiple factor authentication with, HOTP/TOTP, FIDO2, TLS Certificates, etc. extensible via plugins

Glewlwyd HTTP Basic Authentication Schema documentation

License: CC BY 4.0


The HTTP Basic Authentication performs a login/password authentication against a specified webservice that requires HTTP Basic Authentication. This scheme is similar to HTTP authentication backend but requires users to be already added to any backend (Database or LDAP). The advantage is that you can specify different scopes for each users and add any other additional data for the users.


In the administration page, go to Parameters/Authentication schemes and add a new scheme by clicking on the + button. In the modal, enter a name and a display name (the name must be unique among all authentication scheme instances), and a scheme session expiration in seconds. Select the type HTTP Basic Authentication in the Type drop-down button.

Below is the definition of all parameters.


Name (identifier) of the scheme, must be unique among all the scheme instances, even of a different type.

Display name

Name of the instance displayed to the user.

Expiration (seconds)

Number of seconds to expire a valid session.

Max use per session (0: unlimited)

Maximum number of times a valid authentication with this scheme is possible. This is an additional parameter used to enforce the security of the session and forbid to reuse this session for other authentications.

Allow users to register

If this option is unchecked, only administrator can register this scheme for every user via the administration page.


URL of the HTTP service to connect to.

Validate server certificate

Check this option if the HTTP service uses TLS and if you want to validate the certificate.

Username format on HTTP server

This option can be used to build the auth_basic_user value using the user properties values in a specified format. You can use any user property values as long as it is not a list. The property must be specified surrounded by {}.

Format examples:

  • {username}@glewlwyd.tld
  • {domain}/{username}
  • {specific_property}_{phone}