# Authentication API user info returns unauthorized

**URL:** <https://community.auth0.com/t/authentication-api-user-info-returns-unauthorized/7962>\
**Category:** Get Help\
**Tags:** unauthorized, authentication\_api, user-info, token-info\
**Created:** [August 24, 2017, 5:03pm UTC](https://community.auth0.com/t/authentication-api-user-info-returns-unauthorized/7962 "2017-08-24T17:03:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pipsmarketsapp](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/pipsmarketsapp/32/36592_2.png) [@pipsmarketsapp](https://community.auth0.com/u/pipsmarketsapp)\
**Post date:** [August 24, 2017, 5:03pm UTC](https://community.auth0.com/t/authentication-api-user-info-returns-unauthorized/7962/1 "2017-08-24T17:03:54Z")

</div>

We try to use “user info” instead of legacy “token info”

> **[Authentication API - Auth0 Docs](https://auth0.com/docs/api/authentication?http#user-profile)**
>
> The Authentication API enables you to manage all aspects of user identity when you use Auth0. It offers endpoints so your users can log in, sign up, log out, access APIs, and more.

But it always returns “unauthorized” even though the access token is verified.

We use Lock 10 Widget with the following settings to get scope set to “openid”

```
auth : {
            responseType : "token",
            redirect : false,
            params : {
              scope : "openid"
            }
          }

```

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [August 31, 2017, 4:15pm UTC](https://community.auth0.com/t/authentication-api-user-info-returns-unauthorized/7962/2 "2017-08-31T16:15:36Z")

</div>

I could not reproduce this situation, the `401 - Unauthorized`, unless I provided an incorrect access token.

Based on your usage of Lock I would assume the access token you’re using is an opaque access token, around 16 characters, but can you confirm this situation.

In addition, it may be useful to update the question with the exact contents of the `WWW-Authenticate` response header you get along with the `401`.

---

<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:** [March 2, 2018, 5:56am UTC](https://community.auth0.com/t/authentication-api-user-info-returns-unauthorized/7962/3 "2018-03-02T05:56:07Z")

</div>


