Skip to main content

Integrate with Wasabi

Support level: Community

What is Wasabi?​

Wasabi is an S3-compatible cloud object storage service.

-- https://wasabi.com

Preparation​

The following placeholders are used in this guide:

  • authentik.company is the FQDN of the authentik installation.
info

This documentation lists only the settings that you need to change from their default values. Be aware that any changes other than those explicitly mentioned in this guide could cause issues accessing your application.

info

Single sign-on is only available for paid Wasabi accounts. The SSO settings do not appear on trial accounts.

authentik configuration​

To support the integration of Wasabi with authentik, you need to create a SAML property mapping, an application/provider pair, and application entitlements for the Wasabi SSO roles that users should receive.

Create a role property mapping​

Wasabi reads the user's roles from a SAML attribute named groups and matches each value against the name of a Wasabi SSO role.

  1. Log in to authentik as an administrator and open the authentik Admin interface.
  2. Navigate to Customization > Property Mappings and click Create.
  3. Select SAML Provider Property Mapping as the type and click Next.
  4. Configure the property mapping:
    • Name: provide a descriptive name, such as Wasabi roles.
    • SAML Attribute Name: groups
    • Expression: 
      return [
          entitlement.name
          for entitlement in request.user.app_entitlements(provider.application)
      ]
  5. Click Finish.

Create an application and provider​

SAML provider changes in authentik 2026.5

authentik 2026.5 introduces changes to how the SAML provider behaves. Specifically, the provider now automatically sets the Issuer value to: https://authentik.company/application/saml/<application_slug>/metadata/

Older versions of authentik set this value to authentik by default. If you're running an older version, please set Issuer to https://authentik.company/application/saml/<application_slug>/metadata/, where <application_slug> is the slug that you selected for the application.

  1. Log in to authentik as an administrator and open the authentik Admin interface.

  2. Navigate to Applications > Applications and click New Application to open the application wizard.

    • Application: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings.

    • Choose a Provider type: select SAML Provider as the provider type.

    • Configure the Provider: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations:

      • Set ACS URL to https://sso.wasabisys.com/login/callback.
      • Set Audience to https://sso.wasabisys.com/saml.
      • Set Service Provider Binding to Post.
      • Under Advanced protocol settings:
        • Set an available Signing Keypair, and enable Sign assertions and Sign responses.
        • Under Property mappings, add the Wasabi roles mapping.
        • Set NameID Property Mapping to authentik default SAML Mapping: Email.

    • Configure Bindings (optional): you can create a binding (policy, group, or user) to manage the listing and access to applications on a user's Application Dashboard page.

  3. Click Submit to save the new application and provider.

Download metadata file​

  1. Log in to authentik as an administrator and open the authentik Admin interface.
  2. Navigate to Applications > Providers and click on the name of the provider that you created in the previous section.
  3. Under Related objects > Metadata, click Download. This downloaded file is your SAML metadata file and is required in the next section.

Create application entitlements​

Use application entitlements to represent the Wasabi SSO roles that this application should send.

  1. In the Admin interface, navigate to Applications > Applications and open the Wasabi application.
  2. Click the Application entitlements tab.
  3. Click Create, enter a name for the Wasabi SSO role, such as wasabi-admins, and click Create again.
  4. Bind the appropriate users or groups to the entitlement.
  5. Repeat these steps for each Wasabi SSO role that authentik should send.

Wasabi configuration​

Configure the SSO connection​

  1. Log in to the Wasabi Console as the root user.
  2. Navigate to Security > SSO (Single Sign On).
  3. Set Organization Name to a unique name for your organization. Users enter this name when they sign in with SSO.
  4. Set SSO Connection to SAML.
  5. Under IDP Metadata XML, upload the metadata file that you downloaded in Download metadata file.
  6. Click Save.

Create SSO roles​

Wasabi grants permissions to federated users through SSO roles. The name of each SSO role must match an application entitlement name in authentik.

  1. On the SSO (Single Sign On) page, click Create Role.
  2. Set Name to the name of an application entitlement from authentik, such as wasabi-admins, and click Next.
  3. Attach the policies that the role should grant, such as AdministratorAccess, and click Create Role.
  4. Repeat these steps for each application entitlement that should grant access to Wasabi.
info

Wasabi signs in a federated user whose email address matches the Wasabi root user's email address as the root user, rather than with an SSO role.

Configuration verification​

To confirm that authentik is properly configured with Wasabi, log out of the Wasabi Console. On the login page, click Sign In with SSO, then Sign In With an Organization Name, and enter the organization name that you configured in Wasabi.

After you are redirected to authentik and successfully authenticate, the Wasabi Console signs you in.

Resources​