habsi/authentik
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
582812b3ec5df24a556f41e76b925647788038e2
authentik/docs/topics/users-sources/sources/social-logins/twitter/index.md
Teffen Ellis 582812b3ec website: Flesh out docs split. 
website: Copy files during build.

website: Allow for mixed env builds.

website: Reduce build size.

website: Expose build.

website: Add build memory debugging.

WIP: Disable broken links check to compare memory usage.

website: Update deps.

website: Clean up API paths.

website: Flesh out 3.8 fixes.

Format.

website: Update ignore paths.

Website: Clean up integrations build.

website: Fix paths.

website: Optimize remark.

website: Update deps.

website: Format.

website: Remove linking.

website: Fix paths.

wip: Attempt API only build.

Prep.

Migrate render to runtime. Tidy sidebar.

Clean up templates.

docs: Move directory. WIP

docs: Flesh out split.

website: Fix issue where routes have collisions.
2025-07-01 21:53:19 +02:00

1.6 KiB
Raw Blame History

title, support_level
title support_level
Twitter authentik

Allows users to authenticate using their twitter credentials

Preparation

The following placeholders are used in this guide:

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

Twitter

You will need to create a new project, and OAuth credentials in the Twitter Developer console.

  1. Visit https://developer.twitter.com/ to create a new App
  2. Select an environment fitting to your use-case
  3. Give the app a name, for example authentik
  4. Finish setting up the app by clicking App settings. Any of the API keys on this screen are not used by authentik.
  5. Click the Set up button

  1. Enable OAuth 2.0
  2. Set Type of App to Web
  3. Set Callback URI / Redirect URL to https://authentik.company/source/oauth/callback/twitter/
  4. Set Website URL to https://authentik.company

  1. Confirm with Save
  2. Copy and store Client ID and Client Secret for later

authentik

  1. Under Directory -> Federation & Social login Click Create Twitter OAuth Source

  2. Name: Choose a name (For the example I use Google)

  3. Slug: twitter (If you choose a different slug the URLs will need to be updated to reflect the change)

  4. Consumer Key: Your Client ID from step 25

  5. Consumer Secret: Your Client Secret from step 25

:::note For instructions on how to display the new source on the authentik login page, refer to the Add sources to default login page documentation. :::