Setup a hosted discourse instance and trying the Drupal Discourse Module: Client Challenge Reading the Drupal module’s README says: Log into the Discourse instance as an admin and go to the site settings screen /admin/site_settings Set force_hostname to be the Drupal url and path in Discourse site settings. Eg drupalsite.com/discourse This will give correct links in emails sent by Discourse. Your forum should now be available at /discourse “force_hostname” doesn’t exist in my Discourse instance. Has this been deprecated? Also noticed the Drupal Module was tested with Discourse 1.2.0.beta5 and Discourse is on ver 1.4. Has anybody tried this module with newest Discourse? Does it work?

Hi, there is another SSO solution for Drupal 7 and Discourse tested on beta13. Download discourse 7.x-1.5 module. Install module and dependency (querypath) Go to Configuration - System - Discourse: [изображение] in my case forum works from folder /forum. Set SSO endpoint (/discourse_sso) and secret in Discourse settings: [245] You may use both discourse sso plugins mentioned above.

[image] tbecker: Set force_hostname to be the Drupal url and path in Discourse site settings. Eg drupalsite.com/discourse This will give correct links in emails sent by Discourse. That’s very wrong. The referenced setting is restricted to development mode only because of people doing stupid things like that. [image] tbecker: Your forum should now be available at /discourse Sounds like it’s trying to set up subfolder. You can do that with hosted forums, but it’s a bit expensive. Reading the page, seems like it doesn’t offer much other than SSO? In that case, might as well skip it.

If you want our official supported SSO follow this topic [image] Setup DiscourseConnect - Official Single-Sign-On for Discourse (sso) Integrations DiscourseConnect is a core Discourse feature that allows you to configure “Single Sign-On (SSO)” to completely outsource all user registration and login from Discourse to another site. Offered to our pro, business and enterprise hosting customers. information_source (Feb 2021) ‘Discourse SSO’ is now ‘DiscourseConnect’. If you are running an old version of Discourse, the settings below will be named sso_... rather than discourse_connect_... The Problem Many sites wishing to integrate wit…

The module is trying to embed Discourse into Drupal, so instead of using Drupal Forums you’re using Discourse. Doesn’t look like the module works though. It’s doing some whacky monkey patch with Ember to get Discourse to run on the Drupal page. Not looking like a robust, quick and easy solution to get Discourse in Drupal.

If you want to embed discourse, follow our official supported instructions at [image] Embed Discourse comments on another website via Javascript Integrations Discourse has the ability to embed the comments from a topic in a remote site using a Javascript API that creates an IFRAME. For an example of this in action, check out Coding Horror’s blog. The blog is run via Ghost but the comments are embedded from his Discourse forum. One important thing to note with this setup is that users have to navigate to your forum to post replies. This is intentional, as we feel that the posting interface on a Discourse forum is currently much richer than what we …

After spending quite a while getting login integration, I finally have OAuth2 working between Discourse and Drupal. See here: [image] OAuth2 integration with Drupal SSO Special thanks to @dashohoxha for his help!! Continuing the discussion from OAuth2 Basic Support: I will use this thread to document my steps and progress in integrating Discourse and Drupal via OAuth2. At present, the status of my implementation is WORKING. Installation on Discourse: For installation on Discourse, do the following: Install OAuth2 Basic plugin as per this thread. See Install a plugin for details on how to install a plugin Configure OAuth2 plugin: You should see an… I hope that saves some time for others! tarek : )

Hi, Let me share our implementation of SSO based on Drupal 7.56 and Discourse 1.9.0.beta7 using discourse_sso plugin. I have tried the plugin on the subject, even OAuth2 integration but the most interesting were this one. Unfortunately, there is no enough information how to force SSO to run, even Readme does not contain useful information. For that reason, I decided to publish my live configuration. [SSO Drupal Discourse] The configuration is: Ubuntu 16.04.1 x86_64 Nginx/1.10.3 Docker 17.06.1-ce Discourse 1.9.0.beta7 Drupal 7.56 Php v7.0.22 Discourse_sso (from github) On test environment, both services, Discourse and Drupal are located on the same server as virtual servers managed by Nginx. Both services are managed by two separate config files (see below). The sources how to install Discourse and Drupal are here and here. I have to mention that Discourse is the main service in our case (because Drupal is more flexible to tune), it uses port 80. But as desired by our team, the forum has moved from root (/) folder to /support folder. The guide I used for this is located here but the settings are described below as well. Next, Drupal website operates on port 8080 on the same server. Forum URL: http://example.com/support Drupal site URL: http://example.com:8080 Config for Drupal /etc/nginx/sites-enabled/drupal: server { listen 8080 default_server; root /var/www/html/drupal; server_name example.com; location / { # This line and below allow to use clean links try_files $uri /index.php?$query_string; } location @rewrite { rewrite ^/(.*)$ /index.php?q=$1; } location ~ ^/sites/.*/files/styles/ { try_files $uri @rewrite; } location ~ \.php$ { include snippets/fastcgi-php.conf; fastcgi_pass unix:/run/php/php7.0-fpm.sock; } } Enable clean URLs in Drupal: Configuration - Search and metadata (block) - Clean URLs - Enable clean URLs To disable a blank screen on root folder apply redirection definition into Nginx config for Discourse: Config for Discourse /etc/nginx/sites-enabled/discourse: server { listen 80; server_name forum.example.com; location /support { proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock:; proxy_set_header Host $http_host; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } # Forward requests from Discourse root to Drupal root location / { proxy_pass http://127.0.0.1:8080; # proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_read_timeout 30m; } } Some additional settings to Discourse app.yml: Add a line to templates: templates: - "templates/web.socketed.template.yml" # <-- Added Comment a line answering for the port 80 redirection: expose: # - "80:80" # http Add to ‘env’ section: DISCOURSE_RELATIVE_URL_ROOT: /support version: 1.9.0.beta7 Modify your ‘run’ section (completely view): run: - exec: cd: $home cmd: - mkdir -p public/support - cd public/support && ln -s ../uploads && ln -s ../backups - replace: global: true filename: /etc/nginx/conf.d/discourse.conf from: proxy_pass http://discourse; to: | rewrite ^/(.*)$ /support/$1 break; proxy_pass http://discourse; - replace: filename: /etc/nginx/conf.d/discourse.conf from: etag off; to: | etag off; location /support/ { rewrite ^/support/?(.*)$ /$1; } - replace: filename: /etc/nginx/conf.d/discourse.conf from: $proxy_add_x_forwarded_for to: $http_fastly_client_ip global: true - exec: cmd: - sed -i '/no-referrer-when-downgrade/a proxy_redirect http:\/\/example.com\/ \/support\/;' /etc/nginx/conf.d/discourse.conf Configure your discourse_sso plugin, download discourse_sso.tar.gz (129.1 KB) [190] Fill Discourse site URL with your Discourse URL (our case: http://example.com/support). Fill SSO secret with your secret token. Go to your Discourse forum as admin and set the following options: [196] enable sso - enabled sso url - (example: http://example.com:8080/discourse/sso, this address should not return 404!) sso secret - fill the same secret token as used above in Drupal. Open your forum in private browser and click ‘Login’. If above settings were configured properly, you will be redirected to Drupal site. Enter your credentials and next second you will be redirected back to the forum. p.s. After applying settings you are not allowed to login locally using your credentials. To prevent lost connection to your forum use private browsing and do not close admin settings, use /users/admin-login to login. If something went wrong, follow the instruction how to disable SSO using rails commands: cd /var/discourse ./launcher enter app rails c irb > SiteSetting.enable_sso = false irb > SiteSetting.enable_local_logins = true irb > exit exit p.p.s. Disable option ‘email editable’ in Discourse admin settings to prevent using a single Drupal account to recreate Discourse user if the email was changed by a user.

Trouble connecting drupal and discourse

Product Support

codinghorror (Jeff Atwood) October 6, 2015, 10:13am 3

If you want our official supported SSO follow this topic

Topic		Replies	Views
Issue with Drupal Discourse SSO SSO discourseconnect	12	2138	October 13, 2020
Integration Discourse into Drupal Product Support	1	723	July 6, 2020
Using Discourse on a Drupal site Product Support	3	1699	August 5, 2018
Drupal 8 and Discourse shared SSO SSO	2	1353	October 17, 2023
Can I authenticate to Drupal via Discourse? Product Support	4	1822	October 25, 2019

Trouble connecting drupal and discourse

Related topics