I’m trying to configure a self-hosted Docker instance of Discourse to authenticate users with SAML, using Okta as the IdP. At first my setup looked identical to what @runofthemill posted here: Discourse-saml + Okta endless redirect. But then, thanks @skoota, I re-set all the native SSO configs to the defaults, since I understand want to be relying just on the plugin.
So now plugin is successfully installed, and SAML appears as a login option, but I get this error when I try to use it:
I took a look at the library this error seems to orginate from, and it’s not obvious to me what’s going wrong. But I’m not a rubyist, so maybe (hopefully!) I’m missing something obvious.
Nope, couldn’t figure it! Thanks for asking though. If you do wind up figuring out how to make them work nicely together, I’d be interested to know what you discover.
I was able to get Okta and Discourse working together nicely via OpenID Connect. I couldn’t figure out Okta via SAML, but it seems like that should be possible.
결국 Auth0를 사용했지만, ‘북마크’ 앱 외에는 사용자가 직접 Auth0로 연결되는 런치패드 링크를 제공하지 못했습니다. 사용자가 Discourse 세션을 가지고 있지 않고 보호된 URL에 접근하면 새로운 세션이 생성되어야 합니다. Discourse에서 다른 모든 로그인 옵션을 비활성화했기 때문에 사용자는 로그인 모달을 전혀 보지 못하게 됩니다. POC(개념 증명)에는 매끄러운 설정이 되었지만, 단일 로그아웃 시나리오는 끝내 해결하지 못했습니다.
