Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Anyway of making a domain account password change (say every 5 minutes) automatically.

Linking to a web app or mobile app would be awesome


share|improve this question

closed as unclear what you're asking by Xavierjazz, Kevin Panko, David, Excellll, Shekhar Jan 17 '14 at 20:47

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question.If this question can be reworded to fit the rules in the help center, please edit the question.

This is an XY problem. You are asking us how to implement a vaguely described solution to an unspecified problem. That won't work. You have to tell us what the problem you are trying to solve is, you can't start the description with your solution. – David Schwartz Jan 16 '14 at 23:00
I need a program which will automatically change a domain users password, so the user would need to login with the most recent password. Large companies sometimes use tags which provide a new password every 20 seconds or so. So looking for a similar method. wanting to implement for one user before rolling it out across the domain. – dave247 Jan 16 '14 at 23:09
Ahh, now it makes sense. You did ask the wrong question. Those things don't work by changing the password on the app end! (If they did, clock skew between the tag and the server would cause logins to fail. You can't implement that kind of scheme by changing the password on the server side.) – David Schwartz Jan 16 '14 at 23:27
up vote 2 down vote accepted

It won't work.

Schemes that change the password frequently require accounting for clock slippage between the user (or his device) and the server. Otherwise, if it's close to a time boundary (and, in many cases, not that close), a user will often get the wrong password.

Also, policies typically need to be enforced. For example, if a password is "used up", generally it is a policy requirement that it not be used again. The user would have to wait for the next password. And, in some cases, you will need to make the user wait for the next password anyway because the slippage is too great.

Schemes such as you describe are implemented by hooking the server's password checking process and intelligently comparing it to the possible passwords the user might send. Changing the password frequently on the server side will not work.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.