Greetings and salutations!
The following is a tale of a 10.0.3 engine with a 10.0.8 Java client.
After a password entering snafu, one of our users used the Documentation tab to restore an older version of a LOGIN object. Much to his surprise, then, a large number of production jobs are currently falling flat. It appears AE does restore old LOGIN objects, but it does NOT restore the passwords contained therein?
We tried this ourselves then, with a simple LOGIN object. Made a job with it, ran it. Purposefully broke the password - observed the job will not run. Use AE's versioning feature to restore the initial version of the LOGIN object, and the job will not run due to an improper password.
We've also looked at the hashes in the database: All "recovered" passwords have pretty much the same hash (except for the first few bytes).
So my question is: Has anyone experienced this, too, and to anyone in an Automic official capacity: Is this by design, and if so, is it documented?
The documentation states that LOGIN objects have versioning, and I didn't find any special notes on LOGIN objects. If true, I think there should be an unmistakeable warning in the client before allowing anyone to restore (potentially large) LOGIN objects.