On 26/06/18 01:49, Alex O'Ree wrote: > Actually I figured it out. It is possible via the mx bean. I'd like to > request that the method isLocked be changed to public in a future version.
Done in 9.0.x for 9.0.11 onwards. Mark > > The use case is not a typical one but I'd like admins to know if a service > account is locked out for some reason and to be able to reset it if > necessary. The timeout is 15 minutes but the account is frequently used by > service processes which causes the timeout to continually get reset (unless > I am misunderstanding the code) > > On Mon, Jun 25, 2018, 7:13 PM Christopher Schultz < > ch...@christopherschultz.net> wrote: > > Alex, > > On 6/25/18 3:24 PM, Alex O'Ree wrote: >>>> Is it possible to programmatically unlock an account that's been >>>> locked via the lockoutrealm and the simple xml user store? > > Regardless of the user-storage mechanism, the answer is no. > >>>> If so, how? > > Sorry. > > What's the use-case, here? Support gets a call saying "please unlock > this account"? What's the lock-timeout in your environment? > > -chris >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
