Server Authz Endpoints invalid configuration example about authelia

[james-d-elliott]

As per the issue template:

Mistakes in the documentation (which should be reported via the Documentation Feedback discussions).

Provide complete logs with the log level set to debug or trace. Complete means from application start until the issue occurring. This is clearly explained in the Logs section of the troubleshooting guide.

[glime-ai]

Please note this response was created using generative AI leveraging previously available information from the repository. This information may be helpful however it is our strong recommendation that you carefully consider the information before blindly applying it.

---

Based on the provided context and the error message in the logs, it appears that the issue stems from an incorrect configuration in the authn_strategies section of the Authelia configuration. Specifically, the strategy name HeaderAuthRequestAuthorization is not recognized as a valid option. The valid strategy names, as indicated by the error message, are CookieSession, HeaderAuthorization, HeaderProxyAuthorization, HeaderAuthRequestProxyAuthorization, or HeaderLegacy.

To resolve this issue, you should replace HeaderAuthRequestAuthorization with one of the valid strategy names in your configuration file. For example, if you intended to use header-based authorization for the Auth Request implementation, you might want to use HeaderAuthorization or one of the other header-related strategies, depending on your specific requirements.

Here is a corrected snippet of the configuration based on the assumption that HeaderAuthorization is the intended strategy:

server:
  endpoints:
    authz:
      auth-request:
        implementation: 'AuthRequest'
        authn_strategies:
          - name: 'HeaderAuthorization'
            schemes:
              - 'Basic'
          - name: 'CookieSession'

Please adjust your configuration accordingly and restart Authelia to apply the changes.

This comment was generated by Glime.