-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSO Not Working #2
Comments
Don't really know what's the issue is.. Its a little bit problematic for me to test it - I just tried to check whether sso is working on my newly created disqus site and it seems all good. Have you tried it - https://disqus.com/api/sso/ ? Is there you user you want to display with you in-site credentials in sso 'users' list? Have he logged in with login sso button? May be the problem is in instance variable where gem tries to get data? I will try to create some test db user model next day and try it out on heroku.. Can't really say what's wrong all I remember that when I was writing gem sso was feature in testing to deploy soon so there is a good probability smth got broken.. |
Hey guys, is the problem with |
As mentioned in the documentation here: https://help.disqus.com/customer/portal/articles/236206-integrating-single-sign-on#configure-domain this.sso = {
name: "SampleNews",
button: "http://example.com/images/samplenews.gif",
icon: "http://example.com/favicon.png",
url: "http://example.com/login/",
logout: "http://example.com/logout/",
width: "800",
height: "400"
}; But, it seems that in our case, within
I'm still digging through the issue, will hopefully try a pull-request once the issue gets fixed. |
I'm using Single-Sign-On with the
disqus_rails
gem, and have it configured properly, but the Disqus thread still shows as though the user is logged-out. I've whitelisted the proper domains in my Disqus account, added debugged the encoded and encrypted data that the gem produces (and it's valid), but the thread still doesn't show up correctly. Any idea on what might be the problem?The text was updated successfully, but these errors were encountered: