Temporary password storage during the Runtime's persistence
One of our customers has the following requirements:
1. After launching the Runtime, the first input to the username and password fields must be done by human.
2. From the second time, the input to the username and password fields must be done by robot.
3. The tenporary password stored by the robot must be secured. Even when the robot crashes, the username and password must not be hacked.
4. The username and password typed by human can be different every time the Runtime is launched, even on the same machine.
I think Assisted Sign-On seems not to suit this particular requirement. Any reasonable approach to meet these requirements?