# Debug and fixing common DiscourseConnect issues

**URL:** https://meta.discourse.org/t/debug-and-fixing-common-discourseconnect-issues/103496
**Category:** Integrations
**Tags:** sso, discourseconnect, how-to
**Created:** [December 4, 2018, 7:44pm UTC](https://meta.discourse.org/t/debug-and-fixing-common-discourseconnect-issues/103496 "2018-12-04T19:44:22Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [May 31, 2019, 11:06pm UTC](https://meta.discourse.org/t/debug-and-fixing-common-discourseconnect-issues/103496/7 "2019-05-31T23:06:41Z")

</div>

You can find the user’s WordPress ID by going to their user page from the WordPress dashboard. The user’s ID will be displayed in the address bar of your browser as the value of the `user_id` query parameter.

Once you have the user’s WordPress ID, you can update their SSO record on Discourse following the steps outlined for updating the `external_id` at the end of the ‘Solving require\_activation SSO login issues’ section of my original post. You need to be careful with this though - especially with admin accounts.

---

_[View the full topic](https://meta.discourse.org/t/debug-and-fixing-common-discourseconnect-issues/103496)._