With Tessitura V15 we have run into problems where "captive" system accounts stop working because their password needs to be reset. This behavior is new to us in Tessitura V15.
As we understand it with Tessitura Version 15 there are now stronger password restrictions. An account can't be used at all until the password is re-set. In the past these accounts would continue to perform their report and other function. You just could not log-in to the client with these accounts until the password was reset.
So, we are using a "captive account" for processes like:
When these passwords expire the services above just stop working.
Have other folks run into this situation?
What are folks doing to manage this so that services continue to operate 7x24x365 as expected, and you don't personally have to go in and make changes each time the expiration is about to occur?
--Tom
Unknown said:Have other folks run into this situation?
Yes, recently one of our non-interactive, system logins, I think it may have been "nscanapi", expired. Some sort of scheduled reminder would be fine, but passwords on accounts like these should never just expire, imho.
I've added code to update T_METUSER, for selected accounts, that runs nightly and sets the expire dt far into the future, if it isn't.
Chris Jensen
How is that chunk of code working out for you? I was considering making this into a job as well.
Unknown said:How is that chunk of code working out for you?
Just fine. I added it to a daily scheduled job that does mostly data hygiene updates, but now also runs:
-- I never want a Tess non-login system account password to "expire" again. we'll reset them on our schedule...update T_METUSER set pw_expr_dt = '12/31/2099'where location in ('ITS','System Resource') and inactive = 'N'and userid in ([various system logins here])and pw_expr_dt < '12/31/2099'