# Using Primetime SSO & wp-discourse plugin

**URL:** <https://meta.discourse.org/t/using-primetime-sso-wp-discourse-plugin/27447>\
**Category:** WordPress\
**Tags:** sso, wordpress, discourseconnect\
**Created:** [11.Апрель.2015 10:45:24 UTC](https://meta.discourse.org/t/using-primetime-sso-wp-discourse-plugin/27447 "2015-04-11T10:45:24Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![pjv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pjv/32/115994_2.png) [@pjv](https://meta.discourse.org/u/pjv)\
**Post date:** [12.Апрель.2015 14:43:24 UTC](https://meta.discourse.org/t/using-primetime-sso-wp-discourse-plugin/27447/10 "2015-04-12T14:43:24Z")

</div>

FWIW, in my environment (running wordpress on a highly optimized and slightly esoteric stack that includes HHVM, nginx with fastcgi-cache, redis object caching, etc) the SSO of the wp-discourse plugin does not work, whereas the PrimeTime SSO works perfectly. I spent a day trying to debug the issue with the wp-discourse plugin on my setup, but couldn’t figure it out. So I am using both for that reason.

It’s odd because when you dig into the code in both plugins, they are clearly based on the same original code. As far as I could tell, the wp-discourse plugin doesn’t seem to be correctly registering the hook/action for the function that is supposed to be handling the SSO requests coming from Discourse. I couldn’t figure out why.

There are others having the same issue. Here is a GitHub thread about it: [https://github.com/discourse/wp-discourse/issues/115](https://github.com/discourse/wp-discourse/issues/115)

---

_[View the full topic](https://meta.discourse.org/t/using-primetime-sso-wp-discourse-plugin/27447)._
