# RFC 7662 support

**URL:** <https://community.auth0.com/t/rfc-7662-support/69519>\
**Category:** Get Help\
**Created:** [September 13, 2021, 7:17am UTC](https://community.auth0.com/t/rfc-7662-support/69519 "2021-09-13T07:17:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sam.g](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sam.g/32/31685_2.png) [@sam.g](https://community.auth0.com/u/sam.g)\
**Post date:** [September 13, 2021, 7:17am UTC](https://community.auth0.com/t/rfc-7662-support/69519/1 "2021-09-13T07:17:55Z")

</div>

Hey there Auth0,

[RFC 7662](https://datatracker.ietf.org/doc/html/rfc7662) for secure OAuth2 Token Introspection is broadly required to leverage OAuth2 powered by Auth0. Is there any particular reason why Auth0 doesn’t provide an endpoint to support this standard, despite feature requests for a number of years now? For instance, are there security flaws or other worrisome reasons why it _couldn’t_ be implemented by Auth0?

Since this has been requested a few times, is this feature on the roadmap, and if not, how would one go about petitioning or lobbying to see it scheduled?

---

<div class="post-metadata">

**Author:** ![dan.woda](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dan.woda/32/18340_2.png) [@dan.woda](https://community.auth0.com/u/dan.woda)\
**Post date:** [September 13, 2021, 9:52pm UTC](https://community.auth0.com/t/rfc-7662-support/69519/3 "2021-09-13T21:52:07Z")

</div>

Hi @sam.g,

There is an open feature request [here](https://community.auth0.com/t/introspection-endpoint-for-opaque-tokens-or-more-flexible-rules-to-get-clear-jwt-access-token/63866).

If you don’t mind, please post there with information about your use case.

---

<div class="post-metadata">

**Author:** ![sam.g](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/sam.g/32/31685_2.png) [@sam.g](https://community.auth0.com/u/sam.g)\
**Post date:** [September 21, 2021, 10:50pm UTC](https://community.auth0.com/t/rfc-7662-support/69519/4 "2021-09-21T22:50:07Z")

</div>

hey there @dan.woda, thank you. although i see that the feature request opened at that link was only recently filed on June 3rd of this year. is that correct?

if so, does that ticket factor in all the previous requests relating to RFC7662? do i take your response to mean it is _not_ on the roadmap, or can you clarify that it is? this is affecting our decision to purchase enterprise in real time

---

<div class="post-metadata">

**Author:** ![dan.woda](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/dan.woda/32/18340_2.png) [@dan.woda](https://community.auth0.com/u/dan.woda)\
**Post date:** [September 22, 2021, 8:51pm UTC](https://community.auth0.com/t/rfc-7662-support/69519/5 "2021-09-22T20:51:24Z")

</div>

> [@sam.g](#):
>
> i see that the feature request opened at that link was only recently filed on June 3rd of this year. is that correct?

That is correct.

> [@sam.g](#):
>
> if so, does that ticket factor in all the previous requests relating to RFC7662?

A feature request topic won’t reflect interest previous to the date it was posted. Users can upvote the topic to indicate their interest.

> [@sam.g](#):
>
> do i take your response to mean it is _not_ on the roadmap, or can you clarify that it is?

It is not currently on our release calendar.

> [@sam.g](#):
>
> this is affecting our decision to purchase enterprise in real time

Are you working with our sales team? These would be good questions for them and would help advocate for your interest in this feature.

---

<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:** [October 7, 2021, 8:51pm UTC](https://community.auth0.com/t/rfc-7662-support/69519/6 "2021-10-07T20:51:38Z")

</div>

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