Can you check if the
invite only admin setting is selected? That may be preventing accounts from being created.
Can you check if the
Yep, that was it after much clicking around. Can you update your post for that part?
Now, I am trying to figure out how to get rid of the sign up/login in the middle if the user is not setup on discourse yet.
Great! I would not rely on that reply. The first post which should have definitive instructions. If those are not clear enough/up to date we will have to work on that!
Glad you got it working.
Is there a way to avoid “losing” the original route when logging in to a private post?
If we visit a private page and hit either of the login buttons on that page, when redirected back to the site, we end up on the categories page.
Hi, using OpenID connect plugin I am able to authenticate user where IdP is Keycloak. I want to map groups or roles (realm or client) associated with user in Keycloak to discourse.
Is it possible with OpenID connect plugin or is it possible with DiscourseConnect?
I am little confused between OpenID connect plugin and discourse connect. Please help.
3 posts were split to a new topic: How to configure the OIDC to set the Username as the email account name or a username like value returned from my auth providers?
I managed to connect GitLab and Microsoft (Azure) with this plugin. btw: for the Azure AD service, make sure to use the “Application Client ID” as client id, not the secret ID or value).
How is it possible to connect Discourse with two OIDC providers, e.g. GitLab and Azure?
EDIT: I managed to get GitLab Login working with OAuth2, so my question is now more “theoretical”.
How exactly do you use the ‘claims’ here?
I am not entirely sure how and what that config option is used for.
I think that you would need to fork the plugin and change its name to be able to configure it twice. Maybe you’d fork it and hard code it for one of those services.
Is this plugin also releveant or connected to Discourse Connect at all?
I noticed that if I use the discourse connect override name or username settings, and also affects this plugin. I looked in the source code of the plugin but could not find anything related to those settings.
There’s no connection to DiscourseConnect. The auth_override_* settings apply to all authentication methods. The code for that is part of Discourse core, so that’s why you won’t see them mentioned in the plug-in’s code.
oh gotcha, makes sense. thanks!
Hi @david Thanks for this plugin. I’m getting it configured, and I have a few questions:
- Is it possible to change the name of the provider from “OpenID Connect” to a name that is indicative of my authentication provider?
- Is it possible to force users to use the OpenID Connect provider and eliminate the ability to create a user with username/password? Our goal is to only allow users that already have an account with our identity provider to use our Discourse instance.
- If #2 is true, is it possible to circumvent this screen/modal altogether and immediately redirect to the configured OpenID Connect provider when “Log In” is clicked?
I answered #2 myself. It looks like you can disable “local logins” (i.e. username/password) in the settings:
openid connect enabled setting, the text says
... Customize user interface text here and the link is
#3 happens automatically when you disable local logins.
Can you please take a look at the issue mentioned in following post? I would like to use OIDC plugin over OAuth basic. But I face the same issue - cannot pass parameters to /authorize request. I put the value in plugin in format of foo=bar.
Is someone ever able to configure OIDC with authorize parameters? Or I have to change to OAuth basic plugin? Many thanks!
Hey @Avinash_Dane Were you able to figure this out ?
I haven’t been able to get this to work in LinkedIn. Curious if anyone else has? I get as far as logging into LinkedIn after being redirected there when clicking on the signin with…button and then “allowing” my app to use my email from LinkedIn, then I get “Sorry there was an error authorizing your account. Please try again.”