Title: WordPress SSO Login Box
Last modified: August 22, 2016

---

# WordPress SSO Login Box

 *  Resolved [tjdurden](https://wordpress.org/support/users/tjdurden/)
 * (@tjdurden)
 * [11 years, 9 months ago](https://wordpress.org/support/topic/wordpress-sso-login-box/)
 * [@ryanv12](https://wordpress.org/support/users/ryanv12/)
 * Wondering if you could give some insight into how the login process for WordPress/
   Disqus SSO should work please.
 * At present, when a user clicks the ‘Sign in with [Site Name]’ button that’s added
   after enabling SSO, it creates a WP login popup window. After entering credentials,
   the window simply takes the user to the site homepage.
 * I’ve seen countless questions around this, but some guidance would be most appreciated.
   The information on [https://help.disqus.com/customer/portal/articles/1148635](https://help.disqus.com/customer/portal/articles/1148635)
   just isn’t helpful (the W3Schools ref even less so!).
 * Kind regards,
    [@tjdurden](https://wordpress.org/support/users/tjdurden/)
 * [https://wordpress.org/support/plugin/disqus-comment-system](https://wordpress.org/support/plugin/disqus-comment-system)
 * [https://wordpress.org/plugins/disqus-comment-system/](https://wordpress.org/plugins/disqus-comment-system/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Contributor [ryanv12](https://wordpress.org/support/users/ryanv12/)
 * (@ryanv12)
 * [11 years, 9 months ago](https://wordpress.org/support/topic/wordpress-sso-login-box/#post-5478297)
 * When the SSO login is opened, the Disqus embed is “listening” for that window
   to close before reloading the page (so the user is logged in). Because the standard
   WordPress login flow isn’t aware of what’s happening, it simply redirects to 
   the home page after logging in.
 * Ideally the plugin will render its own custom login form or do something that
   closes its own window after logging in, but alas that’s not implemented.
 * You can always skip showing the site’s login button entirely and let them log
   in through other means already on your site.
 *  [mienque](https://wordpress.org/support/users/mienque/)
 * (@mienque)
 * [11 years, 9 months ago](https://wordpress.org/support/topic/wordpress-sso-login-box/#post-5478421)
 * Hello,
    I hope Disqus will fix this bug in the next update. For the time being,
   I have made SSO login work partly by adding bellowing script in WordPress to 
   make popup windows close:
 *     ```
       /* Auto Close Windows if login
       ================================== */
       if ( is_user_logged_in() ) {
           echo "<script>window.close();</script>";
       }
       ```
   
 * Just tested it work on Desktop and Android device but for iOS devices the popup
   tab did not close.
 *  [kingstakh](https://wordpress.org/support/users/kingstakh/)
 * (@kingstakh)
 * [11 years, 4 months ago](https://wordpress.org/support/topic/wordpress-sso-login-box/#post-5478540)
 * [@mienque](https://wordpress.org/support/users/mienque/)
    Work great! thanx!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘WordPress SSO Login Box’ is closed to new replies.

 * ![](https://ps.w.org/disqus-comment-system/assets/icon.svg?rev=1636350)
 * [Disqus Comment System](https://wordpress.org/plugins/disqus-comment-system/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/disqus-comment-system/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/disqus-comment-system/)
 * [Active Topics](https://wordpress.org/support/plugin/disqus-comment-system/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/disqus-comment-system/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/disqus-comment-system/reviews/)

## Tags

 * [login](https://wordpress.org/support/topic-tag/login/)
 * [SSO](https://wordpress.org/support/topic-tag/sso/)

 * 3 replies
 * 4 participants
 * Last reply from: [kingstakh](https://wordpress.org/support/users/kingstakh/)
 * Last activity: [11 years, 4 months ago](https://wordpress.org/support/topic/wordpress-sso-login-box/#post-5478540)
 * Status: resolved