How to test password policies that are set to expire users in many days in the future
search cancel

How to test password policies that are set to expire users in many days in the future

book

Article ID: 44078

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Risk Analytics CA Secure Cloud SaaS - Arcot A-OK (WebFort) CLOUDMINDER ADVANCED AUTHENTICATION CA Secure Cloud SaaS - Advanced Authentication CA Secure Cloud SaaS - Identity Management CA Secure Cloud SaaS - Single Sign On

Issue/Introduction

Password policies allow options to trigger expiration activity long into the future. For example: You can disable the user if the password wasn't changed in 60 days or you can disable the user in 90 days.  How will you test this?  Will you have to wait 60 or 90 days?

Environment

Release: CAIDMB99000-12.6.8-Identity Manager-B to B
Component:

Resolution

There are two basic ways to test this:

1. For testing purposes change your policy to expire in 1 day - this way you can test it the next day. If working then you should 'believe' that it will work similarly after a longer number of days.

2. Change your machine clock to the day before or day of expiration to make it 'as if' the time period (60 days, 90 days, etc.. ) has past. This will or should 'trick' the system to think it's expired so that you can test.