Home » forums » Luminis Platform / System

Accounts being disabled

Submitted by ttamagni on Wed, 2010-01-20 10:19

We have a user whose account keeps keeping disabled in Luminis. It is not because of failed login attempts. What other ways can an account be disabled?

 

Thanks,

TJ

‹ Include statement for Header images Message broker: missing messages on restart? ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Inactivity

Submitted by ToddTrann on Wed, 2010-01-20 12:50.

Check this value:

configman -g security.ias.account.max_days_inactivity

We set ours to 0 (zero) so that account never get marked as inactive.  But you might want yours to expire after a few months of inactivty, so set it as appropriate.

But if it's just one user, this likely isn't the problem.... did you search cp.log for that user's ID?

Todd

user behaviour vs user reports

Submitted by libdms on Thu, 2010-01-21 06:56.

We used to run with 500 days set, as all users have to log in at least once a year. (Students cannot progress with their degree unless they do something in our Portal)

That means that we only have to run something to tamper with the ldap once a year if we want to stop the automatic expiry. (so can check if anyone has been inactive for too long and depending on role switch them to last logged in recently)

However, despite a user not having touched the Portal for 3 years... they report that they definitely registered via the Portal 2 months ago. It transpires that they physically went to one of our admin offices and avoided doing anything the way they are asked to.

The moral of this story is:

The only way to know what has been done is to do it yourself (or make sure you observe a user before you believe what they tell you)

Derek

University of Leeds, UK

Syndicate content