authelia/docs/content/integration/openid-connect/clients/wg-portal/index.md

title, description, summary, date, draft, images, weight, toc, aliases, support, seo

title	description	summary	date	draft	images	weight	toc	aliases	support	seo
WG-Portal	Integrating WG-Portal with the Authelia OpenID Connect 1.0 Provider.		2026-08-06T20:00:00+02:00	false		620	true		level versions integration community true true	title description canonical noindex WG-Portal | OpenID Connect 1.0 | Integration Step-by-step guide to configuring WG-Portal with OpenID Connect 1.0 for secure SSO. Enhance your login flow using Authelia’s modern identity management. false

Tested Versions

• Authelia
  • v4.39.24
• WG-Portal
  • v2.3.1

{{% oidc-common %}}

Assumptions

This example makes the following assumptions:

• Application Root URL: https://wg-portal.{{< sitevar name="domain" nojs="example.com" >}}/
• Authelia Root URL: https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/
• Provider ID: {{< sitevar name="provider-id" nojs="authelia" >}}
• Client ID: {{< sitevar name="client-id" nojs="wg-portal" >}}
• Client Secret: insecure_secret
• Admin Groupname: {{< sitevar name="admin-group" nojs="admins" >}}

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

{{< sitevar-preferences >}}

Configuration

Authelia

The following YAML configuration is an example Authelia client configuration for use with WG-Portal which will operate with the application example:

identity_providers:
  oidc:
    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
    ## See: https://www.authelia.com/c/oidc
    clients:
      - client_id: '{{< sitevar name="client-id" nojs="wg-portal" >}}'
        client_name: 'WG-Portal'
        client_secret: '$pbkdf2-sha512$310000$hDm3SNqIGebGH33JVGnCZA$5XA6C8mg.j2MejL1uJfHwFPEqXbW2K.xufEuIIpwN.0Jn0dKs/LLvRKbPTo7MTOjTpwoAVyZj6BsUTHeBjd3sQ'  # The digest of 'insecure_secret'.
        public: false
        authorization_policy: 'two_factor'
        require_pkce: true
        pkce_challenge_method: 'S256'
        redirect_uris:
          - 'https://wg-portal.{{< sitevar name="domain" nojs="example.com" >}}/api/v0/auth/login/{{< sitevar name="provider-id" nojs="authelia" >}}/callback'
        scopes:
          - 'openid'
          - 'email'
          - 'profile'
          - 'groups'
        response_types:
          - 'code'
        grant_types:
          - 'authorization_code'
        token_endpoint_auth_method: 'client_secret_basic'

Application

To configure WG-Portal there is one method, using the config.yml file.

Config.yml

To configure WG-Portal to utilize Authelia as an OpenID Connect 1.0 Provider, use the following configuration:

auth:
  # Other authentication configurations go here
  oidc:
    - provider_name: {{< sitevar name="provider-id" nojs="authelia" >}}
      display_name: Log in with Authelia
      base_url: https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}
      client_id: {{< sitevar name="client-id" nojs="wg-portal" >}}
      client_secret: insecure_secret
      extra_scopes:
        - email
        - profile
        - groups
      field_map:
        user_identifier: preferred_username
        email: email
        firstname: given_name
        lastname: family_name
        user_groups: groups
      admin_mapping:
        admin_group_regex: ^{{< sitevar name="admin-group" nojs="admins" >}}$

If you do not want to map an admin group just omit the admin_mapping section.

See Also

• WG-Portal OIDC Documentation