# Triggering automatic authentication via OIDC when linking to private topics?
**URL:** https://meta.discourse.org/t/triggering-automatic-authentication-via-oidc-when-linking-to-private-topics/364411
**Category:** SSO
**Tags:** sso, openid-connect
**Created:** [May 1, 2025, 6:08pm UTC](https://meta.discourse.org/t/triggering-automatic-authentication-via-oidc-when-linking-to-private-topics/364411 "2025-05-01T18:08:55Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@tyler.lamparter](https://meta.discourse.org/u/tyler.lamparter)
#### Post date: [May 1, 2025, 6:08pm UTC](https://meta.discourse.org/t/triggering-automatic-authentication-via-oidc-when-linking-to-private-topics/364411/1 "2025-05-01T18:08:55Z")
I’m trying to get the functionality specified in this thread, but with OIDC. This thread seems to only be related to [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true), and when I attempt the same thing for our OIDC config, it doesn’t work. Does anyone have other suggestions on how to accomplish this, or would this require some enhancement to the OIDC plugin?
> [@Triggering automatic authentication via SSO when linking to private topics?](https://meta.discourse.org/t/triggering-automatic-authentication-via-sso-when-linking-to-private-topics/106913):
>
> We are using our own application as the SSO provider to Discourse, and we’re having an issue when linking users to private topics in our Discourse forum from our application, in that authentication is only triggered when clicking the ‘Login’ button. We use our own system as the SSO provider to Discourse. We have a mixture of public and private pages on our Discourse, so we don’t have login\_required set. If a user authenticates in to our system, and we link them to our Discourse root url, they …
---
### Author:  [@tyler.lamparter](https://meta.discourse.org/u/tyler.lamparter)
#### Post date: [May 3, 2025, 11:08pm UTC](https://meta.discourse.org/t/triggering-automatic-authentication-via-oidc-when-linking-to-private-topics/364411/2 "2025-05-03T23:08:06Z")
@tshenry got me squared away. You need to add `?origin=/c/:categoryId`. So in our community, it is `https://connective.celigo.com/auth/oidc?origin=/c/11`.