Allow authentication modules to auto-create users in tt-rss internal database when authenticated successfully.

Automatically login user on remote or other kind of externally supplied authentication, otherwise redirect to login form as normal

Whether to enable password based HTTP authentication to access the GNS3 Server.

Path to a file containing username:password. null means no authentication required to use the service.

Authentication cookie.

The OAuth2 server's authentication URI.

Whether to enable server authentication.

Seconds to store cached auth entries for.

Either a path to a certificate with a client certificate and the key or a list of paths to the files with them.

Choose the type of authentication used

Set X-Auth-Request-User and X-Auth-Request-Email response headers (useful in Nginx auth_request mode)

Password based authentication to access the server

Choose users database file to use for authentication

Authentication type for FreshRSS.

A file containing the auth key

The file managing the authentication for deluge, the format of this file is straightforward, each line contains a username:password:level tuple in plaintext

If true, once a specific ip address authed successfully with user/pass, it is added to a whitelist and may use the proxy without auth.

Authentication type

Allow clients to connect without authentication, i.e. without a valid MUNGE credential.

A file containing the password to access the GNS3 Server.

Path of the authentication file.

Authentication to use when connecting to xpra

Path of the authentication file used to connect to registry.

How users are authenticated storage -- save passwords internally pam -- Linux PAM authentication

The authentication method to use.

Password used for HQPlayer's WebUI

Username used for HQPlayer's WebUI

Port number of Go Ethereum Auth RPC API.

The following authentication modes are available: Open -- Accept connections from anyone, use NickServ for user authentication

Path to the file containing the static authentication secret.

This option can be used to store the username / password credentials with the "auth-user-pass" authentication method

Extra parameters to pass after the auth key

Whether to enable Go Ethereum Auth RPC API.

Either "basic" for a general-purpose authorization protocol or "stealth" for a less scalable protocol that also hides service activity from unauthorized clients.

TURN REST API flag

auth.backends options to set in /etc/nipap/nipap.conf.

Pass HTTP Basic Auth, X-Forwarded-User and X-Forwarded-Email information to upstream.

Listen address of Go Ethereum Auth RPC API.

Enables requiring the cluster to authenticate itself to the client.

Authentication settings

'Static' authentication secret value (a string) for TURN REST API only

The auth adapter type

Use this option to configure advanced authentication methods like EAP

Auth sources options used by SimpleSAMLphp.

Enables requiring daemons to authenticate with eachother in the cluster.

Authentication settings

Optional username to use for authentication.

Name of auth backend to use by default.

Enables requiring clients to authenticate with the cluster to access services in the cluster (e.g. radosgw, mds or osd).

Options for the auth plugin

Path to a file containing the password for authentication.

All authentication providers to provision

The password to set when passing the HTTP Basic Auth header.

The name of this authentication provider

Auth mechanism to use

Whether to skip manual device approval.

The username to store inside the credentials file.

The password to store inside the credentials file.

Path to private key file.

Base URL for the Tailscale API.

OAuth scope specification.

Configuration options to set in the GitLab Pages config file

If this list has a single entry, it will be used as the author when you record a patch

Authentication plugin to attach to this listener

This controls the hostname for the 9front authentication server that users will be authenticated against.

Whether to enable oauth2-proxy.

Whether to enable Pizauth, a commandline OAuth2 authentication daemon .

The OAuth Client ID.

Plugin path to load, should be a .so file.

By default pam-u2f module reads the keys from $XDG_CONFIG_HOME/Yubico/u2f_keys (or $HOME/.config/Yubico/u2f_keys if XDG variable is not set)

Either a path to a certificate with a client certificate and the key or a list of paths to the files with them.

The pizauth package to use.

Path to auth.json file

Whether to serve over TLS.

File path to write the authorized YubiKeys, relative to HOME.

Restrict logins to members of this organisation.

Author of the plugin.

List of authorized YubiKey token IDs

List of virtual hostnames from which to accept requests.

oauth2-proxy allows passing sensitive configuration via environment variables

The oauth2-proxy package to use.

Either a path to a certificate with a client certificate and the key or a list of paths to the files with them.

The list of authentication protocols accepted by this network

The OAuth issuer URL.

The name of the cookie that the oauth_proxy creates.

Restrict logins to members of this team.

The address of the reverse proxy endpoint for oauth2-proxy

Profile access endpoint.

Whether to register as an ephemeral node.

Authentication endpoint

The url root path that this proxy should be nested under.

Extra config to pass to oauth2-proxy.

Authentication to expect from remote

OIDC authentication URL endpoint.

Authorized keys for the root user on initrd

Additional global configuration

Pizauth accounts that should be configured

Pass the request Host Header to upstream.

OAuth provider.

Set HttpOnly cookie flag.