|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Because the "non-expiring" login option doesn't prevent the accurev client from behaving as if the login has expired (for all the reasons set out in the first paragraph of the original problem report).
Personally, I'd call this a bug in accurev. Accurev call it a "feature" of their authentication method![]()
In practice, as you correctly point out, if one uses non-expiring logins then things expire infrequently enough that you're unlikely to get "unauthenticated" twice in rapid succession, but it can (and, IME, has) occurred, just not enough for it to be a major blocking issue.