Misago

Tested Versions #

• Authelia
  • v4.37.5
• Misago
  • misago-image v0.29.1

Before You Begin #

Common Notes #

1. The OpenID Connect 1.0 client_id parameter:
   1. This must be a unique value for every client.
   2. The value used in this guide is merely for demonstration purposes and you can theoretically use nearly any alphanumeric string.
2. The OpenID Connect 1.0 secret parameter:
   1. The value used in this guide is merely for demonstration purposes and you should absolutely not use this in production and should instead utilize the Generating Client Secrets guide.
   2. This string may be stored as plaintext in the Authelia configuration but this behaviour is deprecated and is not guaranteed to be supported in the future. See the Plaintext guide for more information.
3. The Configuration example for Authelia is only a portion of the required configuration and it should be used as a guide in conjunction with the standard OpenID Connect 1.0 Configuration guide.

Assumptions #

This example makes the following assumptions:

• Application Root URL: https://misago.example.com
• Authelia Root URL: https://auth.example.com
• Client ID: misago
• Client Secret: insecure_secret

Configuration #

Application #

To configure Misago to utilize Authelia as an OpenID Connect 1.0 Provider:

1. Sign in to the Misago Admin Panel
2. Visit Settings and click OAuth 2
3. Configure the Following:
   1. Basic settings:
      1. Provider name: authelia
      2. Client ID: misago
      3. Client Secret: insecure_secret
   2. Initializing Login:
      1. Login form URL: https://auth.example.com/api/oidc/authorization
      2. Scopes: openid profile email
   3. Retrieving access token:
      1. Access token retrieval URL: https://auth.example.com/api/oidc/token
      2. Request method: POST
      3. JSON path to access token: access_token
   4. Retrieving user data:
      1. User data URL: https://auth.example.com/api/oidc/userinfo
      2. Request method: GET
      3. Access token location: Query string
      4. Access token name: access_token
   5. User JSON mappings:
      1. User ID path: sub
      2. User name path: name
      3. User e-mail path: email
4. Save the configuration

Authelia #

The following YAML configuration is an example Authelia client configuration for use with Misago which will operate with the above example:

    clients:
      - id: misago
        secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
        public: false
        authorization_policy: two_factor
        scopes:
          - openid
          - profile
          - email
        redirect_uris:
          - https://misago.example.com/oauth2/complete/
        grant_types:
          - authorization_code
        response_types:
          - code
        response_modes:
          - query
        userinfo_signing_algorithm: none

See Also #

• Misago OAuth 2 Client Configuration guide