Automate password reset via catalog item

melsarrazin
Tera Contributor

‎06-25-2025 12:00 PM

I have a requirement to create a catalog item for missing devices. Ideally, we are wanting the manager to send in the catalog item, then the system will automatically reset the users password and email it to the manager. Then we are sending a task to security to remotely secure the device that is missing.

 

I am trying to set this up in Flow Designer. 

melsarrazin_0-1750877763706.png

 

I have the flow working as expected but am getting an error with the actual password reset. 

melsarrazin_1-1750877843674.png

I am unable to figure out how to change the password requirements or why ResetADUserPasswordAction.ps1 is failing. 

 

We are currently utilizing Service Desk and Self-Service Password Resets to reset users AD password. 

0 Helpfuls
  • 727 Views
8 REPLIES 8

jonsan09
Giga Sage
Giga Sage

‎06-25-2025 01:53 PM

It might be your organizations password complexity requirements set within Active Directory that is causing the error. Have you validated the requirements with your AD team? (number of characters, type of characters, password history, blacklisted passwords, etc.) Once you have the requirements you should be able to validate that your generated password or static password meet those requirements.

0 Helpfuls

melsarrazin
Tera Contributor
In response to jonsan09

‎06-26-2025 07:08 AM

That is what I am thinking as well but I am wondering how to change the generated password and/or static password within ServiceNow so it meets the requirements.

0 Helpfuls

jonsan09
Giga Sage
Giga Sage
In response to melsarrazin

‎06-26-2025 11:14 AM

A while back, I had a similar issue and ended up creating a flow action to generate a password that meets the password requirements. You might be able to lean/build off the password generator built into the user table: 

0 Helpfuls

Aniket Chavan
Tera Sage
Tera Sage

‎06-26-2025 07:22 AM

Hello @melsarrazin ,

 

Just going by the error message, I’d recommend reaching out to your AD team to fully understand the logic or restrictions they've applied for password resets—like complexity rules, blocked patterns, reuse policies, etc.

 

Once you have that info, you can try implementing those restrictions on the catalog form itself. For example, you could use RegEx validations on the password variable to make sure the input matches your org's password policy before even submitting the request.

 

Alternatively, you could handle some validations inside the Flow Designer as conditions, depending on what checks you need. I'm not exactly sure how to handle restrictions around past password history, but for that, maybe the safest approach is to just add a tooltip or annotation on the field advising the requester not to reuse previous passwords.

 

Hopefully that helps! Let us know your thoughts or if you find something different that works.

 

Please Mark ✅Correct if this solves your query and also mark 👍Helpful if you find my response worthy based on the impact.


Regards,
Aniket

0 Helpfuls