# Auth0 OidcClient and fixed length of Access Token & Authorization Code

**URL:** <https://community.auth0.com/t/auth0-oidcclient-and-fixed-length-of-access-token-authorization-code/79512>\
**Category:** Get Help\
**Tags:** deprecation, oidc, access-token\
**Created:** [March 8, 2022, 4:47pm UTC](https://community.auth0.com/t/auth0-oidcclient-and-fixed-length-of-access-token-authorization-code/79512 "2022-03-08T16:47:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![HueyLake](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@HueyLake](https://community.auth0.com/u/HueyLake)\
**Post date:** [March 8, 2022, 4:47pm UTC](https://community.auth0.com/t/auth0-oidcclient-and-fixed-length-of-access-token-authorization-code/79512/1 "2022-03-08T16:47:01Z")

</div>

Hi everyone,  
for a Xamarin project we are using Auth0.OidcClient last stable packages (3.2.4 for core and Android, 3.3.4 for iOS).  
We are seeing deprecation notices about the migration to variable size access tokens and authorization codes, but the deprecation notices appears at irregular intervals, not directly before or after every login request.  
We send an audience in the request as an extra parameter.

If we force the new behavior via the provided switch we don’t observe any clear problem, but I’m uneasy in just proceeding without a full understanding.

Thanks.

---

<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:** [March 10, 2022, 5:18pm UTC](https://community.auth0.com/t/auth0-oidcclient-and-fixed-length-of-access-token-authorization-code/79512/3 "2022-03-10T17:18:12Z")

</div>

Hi @HueyLake,

Welcome to the Auth0 Community!

Here is our officially deprecations doc for this change: [Deprecations and Migrations](https://auth0.com/docs/troubleshoot/product-lifecycle/deprecations-and-migrations#opaque-access-token-and-authorization-code-fixed-length-)

Let me know if you have any specific questions.

---

<div class="post-metadata">

**Author:** ![HueyLake](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@HueyLake](https://community.auth0.com/u/HueyLake)\
**Post date:** [March 11, 2022, 9:24am UTC](https://community.auth0.com/t/auth0-oidcclient-and-fixed-length-of-access-token-authorization-code/79512/4 "2022-03-11T09:24:07Z")

</div>

Hi @dan.woda,  
thanks for the support!  
What I don’t understand is

1. why we are even seeing the deprecation notices in the logs, using the official library and sending the audience with every request - am I mistaken in thinking we shouldn’t?
2. why the deprecation notices appear only occasionally and not every time, is there some kind of cool-down timing on them?

Thanks!

---

<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:** [March 11, 2022, 4:55pm UTC](https://community.auth0.com/t/auth0-oidcclient-and-fixed-length-of-access-token-authorization-code/79512/5 "2022-03-11T16:55:04Z")

</div>

It’s normal to see a warning or notice in the logs if you are using a feature or a change is coming that could affect your app. As for how often they occur, I’m not sure exactly what to expect here, but I can look into it.

Can you please DM me your tenant name so I can see what you are seeing?

---

<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:** [April 22, 2022, 12:01am UTC](https://community.auth0.com/t/auth0-oidcclient-and-fixed-length-of-access-token-authorization-code/79512/6 "2022-04-22T00:01:33Z")

</div>


