# Discourse as Identity Provider on Authentik

**URL:** https://meta.discourse.org/t/discourse-as-identity-provider-on-authentik/409259
**Category:** Support
**Tags:** sso, oauth2, discourseconnect, auth-plugins
**Created:** [August 4, 2026, 2:06pm UTC](https://meta.discourse.org/t/discourse-as-identity-provider-on-authentik/409259 "2026-08-04T14:06:56Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![satonotdead](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/satonotdead/32/447830_2.png) [@satonotdead](https://meta.discourse.org/u/satonotdead)
#### Post date: [August 4, 2026, 2:06pm UTC](https://meta.discourse.org/t/discourse-as-identity-provider-on-authentik/409259/1 "2026-08-04T14:06:56Z")

</div>

> Coming from [Use Discourse as an identity provider (SSO, DiscourseConnect)](https://meta.discourse.org/t/use-discourse-as-an-identity-provider-sso-discourseconnect/32974)

I wonder if the official [discourse-auth-proxy](https://github.com/discourse/discourse-auth-proxy) is enough for using the Discourse users database as provider for Authentik self-hosted instance, or it still only available to admin logins?

Is this a recommended approach, or would it be better to use Authentik as the source and connect Discourse to it? If both methods would work today, I’d like to keep the interface and the features that Discourse offers, and keep the user base where it is.

I’m open to suggestions and wish to read all your experiences on this.