mirror of
https://github.com/goauthentik/authentik
synced 2026-04-28 18:37:42 +02:00
6ed5cb5249
* website/integrations: rename "Create with Provider" to "New Application" The application list page now uses a split-button labeled "New Application" instead of the old "Create with Provider" dropdown. Update all 113 integration guides to match. * website/docs: update flow, stage, and policy button labels - "Create" → "New Flow", "New Stage", "New Policy" for trigger buttons - "Finish" → "Create Flow", "Create Stage", "Create Policy" for submit - "Create and bind stage" → "New Stage" / "Bind Existing Stage" - "Create" (binding submit) → "Create Stage Binding" * website/docs: update provider button labels - "Create" → "New Provider" for trigger buttons - "Create with Provider" → "New Application" in RAC docs - "Create" → "New Property Mapping", "New RAC Endpoint", "New Prompt" for related entity creation * website/docs: update directory button labels - "Create" → "New Source" for federation/social login pages - "Create" → "New Role", submit → "Create Role" - "Create" → "New Invitation" - Policy binding submit → "Create Policy Binding" * website/docs: update endpoint device and system management button labels - "Create" → "New Endpoint Connector", "New Enrollment Token", "New Device Access Group", "New Flow" - Submit → "Create Device Access Group" - "Create" → "New Notification Rule", "New Notification Transport" - Binding submit → "Create Policy Binding" * Reorganize policy documentation * website/docs: address policy docs review feedback * post-rebase * website/docs: Reorganize policy documentation -- Revisions (#21601) * apply suggestions * Fix escaped. * Fix whitespace. * Update button label. * Fix phrasing. * Fix phrasing. * Clean up stragglers. * Format. --------- Co-authored-by: Dominic R <dominic@sdko.org>
2.4 KiB
2.4 KiB
title, tags
| title | tags | ||
|---|---|---|---|
| Mailcow |
|
Allows users to authenticate using their Mailcow credentials by configuring Mailcow as a federated identity provider via OAuth2.
Preparation
The following placeholders are used in this guide:
authentik.companyis the FQDN of the authentik installation.mailcow.companyis the FQDN of the Mailcow installation.
Mailcow configuration
To integrate Mailcow with authentik you will need to create an OAuth application in Mailcow.
- Log in to Mailcow as an administrator
- Navigate to System > Configuration, and then Access > OAuth2 Apps.
- Click Add OAuth2 client and provide the Redirect URI:
https://authentik.company/source/oauth/callback/mailcow/ - Take note of the Client ID and Client Secret. These values will be required in the next section.
authentik configuration
- Log in to authentik as an administrator and open the authentik Admin interface.
- Navigate to Directory > Federation and Social login, click New Source, and then configure the following settings:
- Select type: select OAuth Source as the source type.
- Create OAuth Source: provide a name, a slug which must match the slug used in the Mailcow
Redirect URIfield (e.g.mailcow), and set the following required configurations:- Protocol settings
- Consumer Key:
<client_ID> - Consumer Secret:
<client_secret> - Scopes (optional): define any further access scopes.
- Consumer Key:
- URL Settings
- Authorization URL:
https://mailcow.company/oauth/authorize - Access token URL:
https://mailcow.company/oauth/token - Profile URL:
https://mailcow.company/oauth/profile
- Authorization URL:
- Protocol settings
- Click Finish to save your settings.
:::info For instructions on how to display the new source on the authentik login page, refer to the Add sources to default login page documentation. :::
:::info Embed new source in flow :ak-enterprise For instructions on embedding the new source within a flow, such as an authorization flow, refer to the Source Stage documentation. :::
Source property mappings
Source property mappings allow you to modify or gather extra information from sources. See the overview for more information.