Hey Phil,
I tried doing this myself. It turns out that login_cpw.do pulls down the global UI Scripts, so I thought, great, this is easy, and added this script to perform a simple redirect:
(function () {
var url = '$pwd_change.do';
if (window.location.pathname.indexOf('/login_cpw.do') > -1) {
jslog('redirecting to ' + url);
window.location = url;
}
})();
This worked. And didn't.
It turns out that ServiceNow force a redirect back to login_cpw.do! That's a 302 redirect you can see below coming from $pwd_change.do.
However, I did find a workaround:
1. Add a custom 'Password needs reset' checkbox to the User table and hide the original one - don't use it.
2. Modify your reset policies to use the new field.
3. Use a custom page (Content Management) to redirect to the $pwd_change page.
Page layout:
Page:
4. Add a Login Rule that checks if the custom 'Password needs reset' is true and then direct to your redirect page.
A couple of points:
- I've only checked this with the standard sign-in approach.
- There are definitely drawbacks (such as the fact the user could circumvent the password reset by just changing the URL), but it may work for what you need and you can probably add more checks to ensure the user does reset their password.
Cheers!
James
Phillip,
We are glad you took advantage of the ServiceNow Community to learn more and to get your questions answered. The Customer Experience Team is working hard to ensure that the Community experience is most optimal for our customers.
If you feel that your question was answered, we would greatly appreciate if you could mark the appropriate thread as "Correct Answer". This allows other customers to learn from your thread and improves the ServiceNow Community experience.
If you are viewing this from the Community inbox you will not see the correct answer button. If so, please review How to Mark Answers Correct From Inbox View.
Thanks,
Shivani Patel
