# Utenti che perdono lo status di gruppo?

**URL:** <https://meta.discourse.org/t/users-losing-group-status/96790>\
**Category:** WordPress\
**Created:** [9 Settembre 2018, 2:09pm UTC](https://meta.discourse.org/t/users-losing-group-status/96790 "2018-09-09T14:09:59Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Edward\_Weiss](https://avatars.discourse-cdn.com/v4/letter/e/51bf81/32.png) [@Edward\_Weiss](https://meta.discourse.org/u/Edward_Weiss)\
**Post date:** [13 Settembre 2018, 7:03pm UTC](https://meta.discourse.org/t/users-losing-group-status/96790/12 "2018-09-13T19:03:53Z")

</div>

> [@simon](#):
>
> > [@Edward\_Weiss](#):
> >
> > The add/remove parameters passed in the SSO payload seem to be setting correctly in the logs, which is even more confusing.
> 
> Have you have enabled the ‘Create or Sync Discourse Users on Login’ option (found on the [WP Discourse](https://github.com/discourse/wp-discourse) SSO Provider tab)? If so, an SSO payload is also sent when a user logs into your WordPress site. This payload also hooks into the `wpdc_sso_params` filter. Unfortunately, the results of this call to Discourse are not logged.
> 
> I’m going to make a small change to the [WP Discourse](https://github.com/discourse/wp-discourse) code today so that the call made when ‘Create or Sync Discourse Users on Login’ is enabled does not happen if the request originates from Discourse.

Yes, this setting is enabled. That probably explains all the seemingly random SSO calls that I see in the logs.

Just for my information and education, could you explain why the change that you are proposing might help?

---

_[View the full topic](https://meta.discourse.org/t/users-losing-group-status/96790)._
