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.8 KiB
title, tags
| title | tags | |||
|---|---|---|---|---|
| X (Twitter) |
|
Allows users to authenticate using their X credentials by configuring X as a federated identity provider via OAuth2.
Preparation
The following placeholders are used in this guide:
authentik.companyis the FQDN of the authentik installation.
X configuration
To integrate X with authentik you will need to create an OAuth application in the X Developer Portal.
-
Log in to the X Developer Portal.
-
Navigate to Projects & Apps > Overview.
-
Click the App Settings icon (cogwheel) next to the Project App that you want to use. For information on creating a new Project App, refer to the X Developer Documentation.
-
Under User authentication settings, click Set up and set the following required fields:
- App permissions:
Read - Type of App:
Web App, Automated App or Bot - Callback URI / Redirect URL:
https://authentik.company/source/oauth/callback/x/ - Website URL:
https://authentik.company
- App permissions:
-
Click Save.
-
Take note of the Client ID and Client Secret. These values will be required in the next section.
-
Click Done.
authentik configuration
To support the integration of X with authentik, you need to create a Twitter OAuth source in authentik.
- 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 Twitter OAuth Source as the source type.
- Create OAuth Source: provide a name, a slug which must match the slug used in the X
Callback URI / Redirect URLfield (e.g.x), and set the following required configurations:- Protocol settings
- Consumer Key: Enter the Client ID from the X Developer Portal.
- Consumer Secret: Enter the Client Secret from the X Developer Portal.
- Scopes (optional): define any further access scopes.
- Protocol settings
- Click Finish.
:::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. :::