authelia/docs/content/integration/prologue/get-started.md

title	description	summary	date	draft	images	weight	toc	seo
Get started	A getting started guide for Authelia.	This document serves as a get started guide for Authelia. It contains links to various sections and has some key notes in questions frequently asked by people looking to perform setup for the first time.	2022-06-15T17:51:47+10:00	false		120	true	title description canonical noindex false

It's important to note that this guide has a layout which we suggest as the best order in areas to tackle, but you may obviously choose a different path if you are so inclined.

Prerequisites

The most important prerequisite that users understand that there is no single way to deploy software similar to Authelia. We provide as much information as possible for users to configure the critical parts usually in the most common scenarios however those using more advanced architectures are likely going to have to adapt. We can generally help with answering less specific questions about this and it may be possible if provided adequate information more specific questions may be answered.

1. Authelia MUST be served via the https scheme. This is not optional even for testing. This is a deliberate design decision to improve security directly (by using encrypted communication) and indirectly by reducing complexity.
2. Your proxy configuration for Authelia MUST include all of the Required Headers.
3. When using the Proxy Authorization the proxy must include all of the required headers for the specific implementation that has been configured, similar to the curated examples.

Forwarded Authentication

Forwarded Authentication is a simple per-request authorization flow that checks the metadata of a request and a session cookie to determine if a user must be forwarded to the authentication portal.

In addition to the https scheme requirement for Authelia itself:

1. Due to the fact a cookie is used, it's an intentional design decision that ALL applications/domains protected via this method MUST use secure schemes (https and wss) for all of their communication.

OpenID Connect 1.0

No additional requirements other than the use of the https scheme for Authelia itself exist excluding those mandated by the relevant specifications.

Important Notes

{{< callout context="danger" title="Important Notes" icon="outline/alert-octagon" >}} The following section has general important notes for users getting started. {{< /callout >}}

• When integrating Authelia with a proxy users should read the specific Proxy Integration Important Notes.

Documentation Variables

Some of the values presented in the documentation can automatically be replaced with documentation variables.

{{< sitevar-preferences >}}

Configuration

It's important to customize the configuration for Authelia in advance of deploying it. The configuration is static and not configured via web GUI. You can find a configuration template named {{< github-link path="config.template.yml" >}} on GitHub which can be used as a basis for configuration, alternatively Authelia will write this template relevant for your version the first time it is started. Users should expect that they have to configure elements of this file as part of initial setup.

The important sections to consider in initial configuration are as follows:

1. jwt_secret which is used to sign identity verification emails for the reset password flow if enabled.
2. authentication_backend which you must pick between LDAP and a YAML File and is essential for users to authenticate.
3. storage which you must pick between the SQL Storage Providers, the recommended one for testing and lite deployments is SQLite3 and the recommended one for production deployments otherwise is PostgreSQL.
4. session which is used to configure:
   1. The session cookies section should be configured with every SSO domain (none of them can be a suffix of the others) you wish to protect, and the most important options in this section are domain and authelia_url.
   2. The secret is the most important, and redis is recommended for production environments.
5. notifier which is used to send 2FA registration emails etc, there is an option for local file delivery but the SMTP option is recommended for production and you must only configure one of these.
6. access_control is also important but should be configured with a very basic policy to begin with. Something like:

access_control:
  default_policy: deny
  rules:
    - domain: '*.{{< sitevar name="domain" nojs="example.com" >}}'
      policy: one_factor

Deployment

There are several methods of deploying Authelia and we recommend reading the Deployment Documentation in order to perform deployment.

Proxy Integration

The default method of utilizing Authelia is via the Proxy Integrations. It's recommended that you read the relevant Proxy Integration Documentation.

{{< callout context="caution" title="Important Note" icon="outline/alert-triangle" >}} When your Deployment is on Kubernetes we recommend viewing the dedicated Kubernetes Documentation prior to viewing the Proxy Integration Documentation. {{< /callout >}}

Additional Useful Links

See the Frequently Asked Questions for helpful sections of the documentation which may answer specific questions.

Moving to Production

We consider it important to do several things in moving to a production environment.

1. Move all secret values out of the configuration and into secrets.
2. Spend time understanding access control and granularly configure it to your requirements.
3. Review the Security Measures and Threat Model documentation.
4. Ensure you have reviewed the Forwarded Headers documentation to ensure your proxy is not allowing insecure headers to be passed to Authelia.
5. Review the other Configuration Options.