# Authorization Extension - data not propagated to JWT

**URL:** <https://community.auth0.com/t/authorization-extension-data-not-propagated-to-jwt/10093>\
**Category:** JWT.io\
**Tags:** authorization-extens\
**Created:** [March 15, 2018, 2:26am UTC](https://community.auth0.com/t/authorization-extension-data-not-propagated-to-jwt/10093 "2018-03-15T02:26:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![vmachacek](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/vmachacek/32/14326_2.png) [@vmachacek](https://community.auth0.com/u/vmachacek)\
**Post date:** [March 15, 2018, 2:26am UTC](https://community.auth0.com/t/authorization-extension-data-not-propagated-to-jwt/10093/1 "2018-03-15T02:26:17Z")

</div>

**- What are you trying to achieve? What is the use case or idea behind it?**

I was trying to configure authorization so its propagated to JWT token, so anyone can read it and act accordingly. The way it is set up at the moment is I configured the rule and my Groups and when I login or fetch my user profile trhu endpoint I cant see any groups there.

When I try to test a rule it shows the groups in the result.

I’m totally new to this, so its very probable I missed something. Thanks for any help..

---

<div class="post-metadata">

**Author:** ![richard.dowinton](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/richard.dowinton/32/16150_2.png) [@richard.dowinton](https://community.auth0.com/u/richard.dowinton)\
**Post date:** [March 16, 2018, 3:44pm UTC](https://community.auth0.com/t/authorization-extension-data-not-propagated-to-jwt/10093/2 "2018-03-16T15:44:22Z")

</div>

Most likely you are now using an [OIDC-conformant flow](https://auth0.com/docs/api-auth/tutorials/adoption/oidc-conformant), in which case you need to modify the rule generated by the authorization extension so that the claims it adds to the access token are namespaced accordingly. See [here](https://auth0.com/docs/api-auth/tutorials/adoption/scope-custom-claims).

Given that when you test the rule the groups show, this is almost certainly the cause of the problem.

---

<div class="post-metadata">

**Author:** ![vmachacek](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/vmachacek/32/14326_2.png) [@vmachacek](https://community.auth0.com/u/vmachacek)\
**Post date:** [March 17, 2018, 4:32pm UTC](https://community.auth0.com/t/authorization-extension-data-not-propagated-to-jwt/10093/3 "2018-03-17T16:32:15Z")

</div>

Hello Richard,

yes, adding the namespace helped me, and when I put the groups data to two properties in the token - one “namespaced” and one without namespace, and than I tried to turn off the `OIDC Conformant` however I was not able to see the version without the namespace in the payload. Do you mind explain me why, please?

Thanks!

---

<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:** [August 16, 2019, 8:10am UTC](https://community.auth0.com/t/authorization-extension-data-not-propagated-to-jwt/10093/4 "2019-08-16T08:10:56Z")

</div>

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