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

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

title	description	summary	date	draft	images	weight	toc	aliases	support	seo
Sure	Integrating Sure with the Authelia OpenID Connect 1.0 Provider.		2025-01-25T12:36:00+11:00	false		620	true		level versions integration community true true	title description canonical noindex Sure | OpenID Connect 1.0 | Integration Step-by-step guide to configuring Sure 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
• Sure
  • v0.6.6

{{% oidc-common %}}

Assumptions

This example makes the following assumptions:

• Application Root URL: https://sure.{{< sitevar name="domain" nojs="example.com" >}}/
  • This option determines the redirect URI in the format of https://sure.{{< sitevar name="domain" nojs="example.com" >}}/auth/openid_connect/callback. This means if you change this value, you need to update the redirect URI.
• Authelia Root URL: https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/
• Client ID: sure
• Client Secret: insecure_secret

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 Sure 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: 'sure'
        client_name: 'Sure'
        client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
        public: false
        authorization_policy: 'two_factor'
        require_pkce: true
        pkce_challenge_method: 'S256'
        redirect_uris:
          - 'https://sure.{{< sitevar name="domain" nojs="example.com" >}}/auth/openid_connect/callback'
        scopes:
          - 'openid'
          - 'email'
          - 'profile'
          - 'groups'
        response_types:
          - 'code'
        grant_types:
          - 'authorization_code'
        access_token_signed_response_alg: 'none'
        userinfo_signed_response_alg: 'none'
        token_endpoint_auth_method: 'client_secret_basic'

Application

To configure Sure there are two methods, using Environment Variables, or using the Web GUI.

Environment Variables

To configure Sure to utilize Authelia as an OpenID Connect 1.0 Provider, use the following environment variables:

Standard

OIDC_ISSUER=https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}
OIDC_CLIENT_ID=sure
OIDC_CLIENT_SECRET=insecure_secret
OIDC_REDIRECT_URI=https://sure.{{< sitevar name="domain" nojs="example.com" >}}/auth/openid_connect/callback
OIDC_BUTTON_LABEL=Sign in with Authelia

Docker Compose

services:
  sure:
    environment:
      OIDC_ISSUER: 'https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}'
      OIDC_CLIENT_ID: 'sure'
      OIDC_CLIENT_SECRET: 'insecure_secret'
      OIDC_REDIRECT_URI: 'https://sure.{{< sitevar name="domain" nojs="example.com" >}}/auth/openid_connect/callback'
      OIDC_BUTTON_LABEL: 'Sign in with Authelia'

Web GUI

To configure Sure to utilize Authelia as an OpenID Connect 1.0 Provider, use the following instructions:

1. Log in as the admin user.
2. Navigate to Settings.
3. In the Advanced section click on SSO Providers.
4. Configure the following options:
   • Strategy: OpenID Connect
   • Name: authelia
   • Button Label: Sign in with Authelia
   • Issuer URL: https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}
   • Client ID: sure
   • Client Secret: insecure_secret
5. Click Test Connection.
6. Click Update Provider.

See Also

• Sure OpenID Provider Documentation