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>
3.1 KiB
title, sidebar_label, support_level
| title | sidebar_label | support_level |
|---|---|---|
| Integrate with Service Name | Service Name | community |
What is Service-Name
Insert a quick overview of what
<service-name>is and what it does. Simply describe the product and what it is, how it is used, and do not include marketing or sales-oriented content.
Preparation
The following placeholders are used in this guide:
service.companyis the FQDN of the<service-name>installation. (Remove this for SaaS)authentik.companyis 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. :::
authentik configuration
To support the integration of <service-name> with authentik, you need to create an application/provider pair in authentik.
Any specific info about this integration can go here.
Create an application and provider in authentik
-
Log in to authentik as an administrator and open the authentik Admin interface.
-
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.
- If there are any specific settings required, list them here. Refer to the ownCloud integration documentation for a complex requirements example.
- Choose a Provider type: If there is a specific provider type required, state that here.
- 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.
- If there are any specific settings required, list them here. Refer to the ownCloud integration documentation for a complex requirements example.
- Configure Bindings (optional): you can create a binding (policy, group, or user) to manage the listing and access to applications on a user's My applications page.
- Application: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings.
-
Click Submit to save the new application and provider.
Service configuration
Insert service configuration
-
Write first step here...
-
Continue with steps....
Configuration verification
Template sentence that you can typically use here: "To confirm that authentik is properly configured with <service-name>, log out and log back in via authentik."
If there are more specific validation methods for the Service (e.g., clicking a button), include these instructions for clarity.
Resources
List the external sources (official docs, community articles, blogs, videos) that were used to create this guide.
- [Bitwarden Help - OIDC Configuration](https://bitwarden.com/help/configure-sso-oidc/)