# Persistent Refresh Token behavior

**URL:** <https://devforum.okta.com/t/persistent-refresh-token-behavior/29262>\
**Category:** OAuth/OIDC\
**Tags:** api\
**Created:** [July 11, 2024, 9:36am UTC](https://devforum.okta.com/t/persistent-refresh-token-behavior/29262 "2024-07-11T09:36:25Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![kulwch](https://avatars.discourse-cdn.com/v4/letter/k/dbc845/32.png) [@kulwch](https://devforum.okta.com/u/kulwch)\
**Post date:** [July 18, 2024, 2:15pm UTC](https://devforum.okta.com/t/persistent-refresh-token-behavior/29262/4 "2024-07-18T14:15:38Z")

</div>

Hi,  
Okta API Scopes can’t be used with the custom Auth servers indeed. And you can’t customize the lifetime for Org Server.

> [@Change the Org Authorization Server Policy/Rules](https://devforum.okta.com/t/change-the-org-authorization-server-policy-rules/23590/2):
>
> The [Org Authorization Server](https://developer.okta.com/docs/concepts/auth-servers/#org-authorization-server) does not support the customizations you are referring to. These options (to create Access Policies and Rules, as well as custom Scopes and Claims) is only available for Custom Authorization Servers. The Org Authorization Server will only issue Access and ID tokens with a 1 hour lifetime.

Does this answer your question ?

---

_[View the full topic](https://devforum.okta.com/t/persistent-refresh-token-behavior/29262)._