<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D5WR00001DPKM30APOkta Classic EngineAdministrationAnswered2026-01-30T17:10:07.000Z2026-01-27T01:30:00.000Z2026-01-30T17:10:07.000Z

mustafam.41248 (Customer) asked a question.

January 27, 2026 at 1:30 AM
Modify the Reset Password Link Lifespan

Hello Okta people,

I have a task to extend the life span of the password reset email for my end users, I followed this article

https://support.okta.com/help/s/article/how-to-modify-the-reset-password-link-lifespan?language=en_US

and when i send the the request to get the policies I'll get all the 3 that I have but when I modify the value of tokenLifetimeMinutes to the required one and POST it the respose in postman will show 200 which is OK but then when i run another get it will still shows 60 minutes.

I saw another post from another admin in here:

https://support.okta.com/help/s/question/0D54z0000AJSSKwCQP/okta-oie-change-reset-password-link-lifespan?language=en_US

and no one helped as you can see.

any help with that would be appreciated

  • 4 answers
  • 63 views

  • Mihai N. (Okta, Inc.)

    Hi @mustafam.41248 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    This not currently officially supported as stated in the article: 

    NOTE: This is just an example. This information should be used at one's own discretion and risk, as the steps could change whenever a product update is released. Okta strongly advises against deploying this in production environments. It is highly recommended to test this in a test/preview environment. All instructions are provided AS IS without warranty of any kind. Okta disclaims all implied warranties, including, without limitation, any implied warranties for a particular purpose.

     

    That being said, you will need to get one policy at a time. So you will need to run the GET Password Policies call once to get all the intended IDs.

    Example:

    Policy 1 - id: 0aasdfasgadd7

    Policy 2 - id: 0aaasdqdsqd8

    Policy 3 - id: 0azvadsvadfo9

     

    Once you get the IDs , you will need to get the policy body for the first one by running a similar call as before but this time for the intended ID instead of ?type=PASSWORD . Something like:

    {{url}}/api/v1/policies/0aasdfasgadd7  - for policy 1 

     

    copy the body 

     

    make changes to the tokenLifetimeMinutes value 

     

    then run Update Password Policy call: 

     

    PUT {{url}}/api/v1/policies/0aasdfasgadd7  where you add the updated body of the request

     

    Then you repeat the process for each intended policy modifying IDs and token values are required. 

     

     

     

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best

  • Mihai N. (Okta, Inc.)

    Hi @mustafam.41248 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    This not currently officially supported as stated in the article: 

    NOTE: This is just an example. This information should be used at one's own discretion and risk, as the steps could change whenever a product update is released. Okta strongly advises against deploying this in production environments. It is highly recommended to test this in a test/preview environment. All instructions are provided AS IS without warranty of any kind. Okta disclaims all implied warranties, including, without limitation, any implied warranties for a particular purpose.

     

    That being said, you will need to get one policy at a time. So you will need to run the GET Password Policies call once to get all the intended IDs.

    Example:

    Policy 1 - id: 0aasdfasgadd7

    Policy 2 - id: 0aaasdqdsqd8

    Policy 3 - id: 0azvadsvadfo9

     

    Once you get the IDs , you will need to get the policy body for the first one by running a similar call as before but this time for the intended ID instead of ?type=PASSWORD . Something like:

    {{url}}/api/v1/policies/0aasdfasgadd7  - for policy 1 

     

    copy the body 

     

    make changes to the tokenLifetimeMinutes value 

     

    then run Update Password Policy call: 

     

    PUT {{url}}/api/v1/policies/0aasdfasgadd7  where you add the updated body of the request

     

    Then you repeat the process for each intended policy modifying IDs and token values are required. 

     

     

     

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    Expand Post
    Selected as Best

    • mustafam.41248 (Customer)

      Hello Mihai,

       

      This is exactly what I did, get all the policies that I have in my case it's 3 policies.

      then copy the ID of the one that need to edit the tokenLifetimeMinutes then run the Get Policy using the ID of the targeted one copy the body for it and edit the tokenLifetimeMinutes from 60 minutes to 120 and then past it in the body of the Update Password Policy using the PUT method and the server replied back with 200 OK which means the update worked right? but when i ran another GET policy to check and make sure the changes were applied it was still showing the 60 minutes.

       

      Expand Post

      • Mihai N. (Okta, Inc.)

        @mustafam.41248 (Customer)​ -That's strange. I ran the process in my test environment (OP3 Preview Cell (US) Version 2026.01.1 E) and when I run a check I get the updated value.

        I recommend reviewing the IDs being used and if needed, open a case to review the implementation with one of our colleagues from the support team. They'll be able to schedule a meeting where you'll be able to go over things together.

        Regards,

        Mihai N.

        -----------------------------------------------------------------

        Visit the Okta Community to search for solutions or ask questions.

        Level up your Identity security superpowers with Okta Learning.

        The new Okta Help Center YouTube channel is your go-to resource for tips, troubleshooting, and best practice videos. Subscribe today.

        Expand Post

  • mustafam.41248 (Customer)

    Yes it is, I'm on the same version as you are OK14 US Cell Version 2026.01.1 E

    E stands for Okta OIE if I'm not mistaken so technically the article should work.

    I did verify everything the API key, ID multiple times.

    I'll reach out to support and see what they say and update you here.

    Thank you.

    Expand Post

Loading
Modify the Reset Password Link Lifespan