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
I've opened a Task Ticket on this. Have others?
I've also tried the following. Suggested by the iWave team.
UPDATE T_METUSERSET pw_expr_dt = '2099-12-31'WHERE userid = ‘XXXXXX'Where XXXXX is the iWave account.
This seems to work. However, I don't know how fragile this is. If someone goes into the security module for some reason and make a change to the rights of one of these accounts. Does the pw_expr_dt get reset to 3 months in the future again?
I had to do the same as we have users that only access TRBO, Tessitura On-the-Go, and/or TNEW Admin. I too have calendar reminders set to remind me to update the password expiration date. I submitted a TASK ticket and their response is that this is expected behavior so I have submitted an enhancement request because users who only have access to the above cannot change their password. I did not think to look at the iWave account so thanks for mentioning it!