Şükrü

2Fauth

postgres

Public URL to connect to Postgres database, used by the Data panel.

Location where the database will be initialized

Default database created when image is started.

2fauth

Set to true if you want to see debug information in error screens.

You can leave this on "local". If you change it to production most console commands will ask for extra confirmation.Never set it to "testing".

The encryption key for  our database and sessions. Keep this very secure. If you generate a new one all existing data must be considered LOST.

The timezone for your application, which is used to record dates and times to database. This global setting can be overridden by users via in-app settings for a personalised dates and times display. If this setting is changed while the application is already running, existing records in the database won't be updated

This variable must match your installation's external address. Webauthn won't work otherwise.

If you want to serve js assets from a CDN (like https://cdn.example.com), uncomment the following line and set this var with the CDN url. Otherwise, let this line emptr.

The default authentication guard Supported:   'web-guard' : The Laravel built-in auth system (default if nulled)   'reverse-proxy-guard' : When 2FAuth is deployed behind a reverse-proxy that handle authentication WARNING When using 'reverse-proxy-guard' 2FAuth only look for the dedicated headers and skip all other built-in authentication checks. That means your proxy is fully responsible of the authentication process, 2FAuth will trust him as long as headers are presents.

Authentication log retention time, in days. Log entries older than that are automatically deleted.

Name of the HTTP headers sent by the reverse proxy that identifies the authenticated user at proxy level. Check your proxy documentation to find out how these headers are named (i.e 'REMOTE_USER', 'REMOTE_EMAIL', etc...) (only relevant when AUTHENTICATION_GUARD is set to 'reverse-proxy-guard')

If you're looking for performance improvements, you could install memcached.

Set this to true to enable Content-Security-Policy (CSP). CSP helps to prevent or minimize the risk of certain types of security threats. This is mainly used as a defense against cross-site scripting (XSS) attacks, in which an attacker is able to inject malicious code into the web app. 

Turn this to true if you want your app to react like a demo. The Demo mode reset the app content every hours and set a generic demo user.

Authentication settings The number of times per minute a user can fail to log in before being locked out. Once reached, all login attempts will be rejected until the minute has elapsed. This setting applies to both email/password and webauthn login attemps.

 The log channel defines where your log entries go to.  'daily' is the default logging mode giving you 7 daily rotated log files in /storage/logs/.  Also available are 'errorlog', 'syslog', 'stderr', 'papertrail', 'slack' and a 'stack' channel  to combine multiple channels into a single one.

Log level. You can set this from least severe to most severe: debug, info, notice, warning, error, critical, alert, emergency If you set it to debug your logs will grow large, and fast. If you set it to emergency probably nothing will get logged, ever.

SSL peer verification. Set this to false to disable the SSL certificate validation. WARNING Disabling peer verification can result in a major security flaw. Change it only if you know what you're doing.

Proxy for outgoing requests like new releases detection or logo fetching. You can provide a proxy URL that contains a scheme, username, and password. For example, "http://username:password@192.168.16.1:10".

Custom logout URL to open when using an auth proxy.

 API settings  The maximum number of API calls in a minute from the same IP.  Once reached, all requests from this IP will be rejected until the minute has elapsed.  Set to null to disable the API throttling.

Use this setting to declare trusted proxied. Supported:   '*': to trust any proxy   A comma separated IP list: The list of proxies IP to trust. 

Relying Party ID, should equal the site domain (i.e 2fauth.example.com). If null, the device will fill it internally (recommended) See https://webauthn-doc.spomky-labs.com/prerequisites/the-relying-party#how-to-determine-the-relying-party-id

WebAuthn settings Relying Party name, aka the name of the application. If blank, defaults to APP_NAME. Do not set to null.

Use this setting to control how user verification behave during the WebAuthn authentication flow. Most authenticators and smartphones will ask the user to actively verify themselves for log in. For example, through a touch plus pin code, password entry, or biometric recognition (e.g., presenting a fingerprint). The intent is to distinguish one user from any other. Supported:   'required': Will ALWAYS ask for user verification   'preferred' (default) : Will ask for user verification IF POSSIBLE   'discouraged' : Will NOT ask for user verification (for example, to minimize disruption to the user interaction flow)