# Authorization Extension Not Adding Permissions, Roles nor Groups to Ticket or Profile

**URL:** <https://community.auth0.com/t/authorization-extension-not-adding-permissions-roles-nor-groups-to-ticket-or-profile/21116>\
**Category:** Get Help\
**Tags:** authorization-extens\
**Created:** [February 9, 2019, 1:03am UTC](https://community.auth0.com/t/authorization-extension-not-adding-permissions-roles-nor-groups-to-ticket-or-profile/21116 "2019-02-09T01:03:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![eric.williams](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/eric.williams/32/10918_2.png) [@eric.williams](https://community.auth0.com/u/eric.williams)\
**Post date:** [February 9, 2019, 1:03am UTC](https://community.auth0.com/t/authorization-extension-not-adding-permissions-roles-nor-groups-to-ticket-or-profile/21116/1 "2019-02-09T01:03:11Z")

</div>

Trying to get a simple scenario configured using the Authorization Extension and I can’t seem to find the correct combination to permission values attached to the user in either access\_token or the app\_meta data properties. The default rule configured from the extension’s dashboard get’s added to my tenant fine but when I test it against my WAAD instance it is always blank. I enabled extensions API was able to confirm /api/users/{userid}/roles was correct.

---

<div class="post-metadata">

**Author:** ![markd](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/markd/32/38919_2.png) [@markd](https://community.auth0.com/u/markd)\
**Post date:** [February 9, 2019, 2:27am UTC](https://community.auth0.com/t/authorization-extension-not-adding-permissions-roles-nor-groups-to-ticket-or-profile/21116/2 "2019-02-09T02:27:35Z")

</div>

Hi @eric.williams,

We had similar problems with the authz extension. In hindsight, I would have avoided storing perms in `app_metadata` and used the authz extension API instead. We found copying the perms to the user’s profile was occasionally flakey, and of course the rule is only trigger on login so authorization changes aren’t reflected in the profile until the user’s next login.

---

<div class="post-metadata">

**Author:** ![eric.williams](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/eric.williams/32/10918_2.png) [@eric.williams](https://community.auth0.com/u/eric.williams)\
**Post date:** [February 10, 2019, 4:42pm UTC](https://community.auth0.com/t/authorization-extension-not-adding-permissions-roles-nor-groups-to-ticket-or-profile/21116/3 "2019-02-10T16:42:24Z")

</div>

To be clear, the access\_token **also** is missing the permissions. In the getPolicy call back logging the data object always returns empty groups, roles and permissions

`console.log('data:', data);`

`data: { groups: [], roles: [], permissions: [] }`

---

<div class="post-metadata">

**Author:** ![James.Morrison](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/james.morrison/32/13507_2.png) [@James.Morrison](https://community.auth0.com/u/James.Morrison)\
**Post date:** [February 11, 2019, 5:44pm UTC](https://community.auth0.com/t/authorization-extension-not-adding-permissions-roles-nor-groups-to-ticket-or-profile/21116/5 "2019-02-11T17:44:53Z")

</div>

Hey there @eric.williams, I apologize for the delay. It looks like you have an open support ticket now on this front. To focus effort I’ll have our internal support team take charge on this matter, however once they devise of a solution I will be sure to share it here as well. Please let me know if there are any additional questions I can relay, thanks!

---

<div class="post-metadata">

**Author:** ![James.Morrison](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/james.morrison/32/13507_2.png) [@James.Morrison](https://community.auth0.com/u/James.Morrison)\
**Post date:** [March 6, 2019, 1:32am UTC](https://community.auth0.com/t/authorization-extension-not-adding-permissions-roles-nor-groups-to-ticket-or-profile/21116/6 "2019-03-06T01:32:06Z")

</div>

For historical record reference and after confirming with the technician, the resolution on this ended up being when using an OIDC login flow you have to add the roles/perms as a custom claim in a separate rule that runs after the authorization extension rule. The extension can only add the roles to the token when the application is a non-oidc conformant app.

---

<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 21, 2019, 1:32am UTC](https://community.auth0.com/t/authorization-extension-not-adding-permissions-roles-nor-groups-to-ticket-or-profile/21116/7 "2019-03-21T01:32:10Z")

</div>

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