# WordPress, missing scope

**URL:** <https://community.auth0.com/t/wordpress-missing-scope/135045>\
**Category:** Get Help\
**Tags:** other-built-in-social-connections, connections\
**Created:** [May 27, 2024, 12:22pm UTC](https://community.auth0.com/t/wordpress-missing-scope/135045 "2024-05-27T12:22:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![edent](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/edent/32/45781_2.png) [@edent](https://community.auth0.com/u/edent)\
**Post date:** [May 27, 2024, 12:22pm UTC](https://community.auth0.com/t/wordpress-missing-scope/135045/1 "2024-05-27T12:22:55Z")

</div>

Ready to post? 🔍 First, try searching for your answer.  
The WordPress social connection has stopped working due to a missing scope parameter.

When I try to log in, I get directed to `https://public-api.wordpress.com/oauth2/authorize?login_hint=&prompt=login&response_type=code&redirect_uri=https%3A%2F%2Fexample.eu.auth0.com%2Flogin%2Fcallback&scope=profile&state=123&client_id=456`

That shows the error:

```txt
Invalid request, please go back and try again.
Error Code: invalid_request
Error Message: Invalid "scope". See https://developer.wordpress.com/docs/oauth2/#token-scope.

```

If I _manually_ add `&scope=auth` to the URl, it allows me to log in.

Note: This was previously working - but something at Auth0’s end has broken in the last few weeks. I have not changed anything in either Auth0 or my WordPress app.

Please can someone from Auth0 fix their built in social connection for WordPress as per [OAuth2 Authentication – WordPress.com Developer Resources](https://developer.wordpress.com/docs/oauth2/#token-scope)

---

<div class="post-metadata">

**Author:** ![edent](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/edent/32/45781_2.png) [@edent](https://community.auth0.com/u/edent)\
**Post date:** [June 25, 2024, 8:29pm UTC](https://community.auth0.com/t/wordpress-missing-scope/135045/2 "2024-06-25T20:29:17Z")

</div>

@dawid.matuszczyk any chance you could ask the team to look at this issue?

---

<div class="post-metadata">

**Author:** ![edent](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/edent/32/45781_2.png) [@edent](https://community.auth0.com/u/edent)\
**Post date:** [August 10, 2024, 9:17am UTC](https://community.auth0.com/t/wordpress-missing-scope/135045/3 "2024-08-10T09:17:10Z")

</div>

Apparently, this is being tracked with reference ESD-38635. No ETA on fix yet.

---

<div class="post-metadata">

**Author:** ![edent](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/edent/32/45781_2.png) [@edent](https://community.auth0.com/u/edent)\
**Post date:** [August 23, 2024, 2:49pm UTC](https://community.auth0.com/t/wordpress-missing-scope/135045/4 "2024-08-23T14:49:13Z")

</div>

This has (finally) been fixed.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [September 6, 2024, 2:50pm UTC](https://community.auth0.com/t/wordpress-missing-scope/135045/5 "2024-09-06T14:50:01Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.