Is there any way to set an "inactive timeout" so that a user is automatically logged out whenever they are inactive for a certain amount of time?

I was using the Automated Logout module, but once I enabled the LDAP modules and configured it, I could no longer automatically logout.

I was just curious if this functionality was already included and I somehow missed it?
Could it possibly be included?

Also, I've looked briefly at the code, but was wandering if there was any hooks created for LDAP? Documentation for them?
If the above isn't implemented, I could do so, but just wanted to know if there were any hooks so I could create a module without having to edit the actual LDAP module.

Thanks!

Comments

johnbarclay’s picture

johnbarclay commented

No thoughts on the auto timeout thing. If automated logout works without ldap, but not with ldap, then its a bug in LDAP or the automated logout module. Both should be using the mechanisms in user.module to logout/check if someone is logged out. Please file a bug in either or both.

As far as hooks, there are a number of them and I'm always willling to add more as needs arise. Depends on what you are up to with your module, but here are some ways to leverage ldap project:
- store queries in ldap_query and execute with ldap query
- store server configurations in ldap_servers
- use ldap feeds fetcher to parse feeds importers
- ldap_servers is the "api" part of the project. ldap_server.functions.inc has some functions.
- extend the ldapServer or ldapAuthorizationConsumerAbstract.class.php

cmurph’s picture

cmurph commented

Thanks @johnbarclay!

I'll post a bug report here (I believe it's an issue with the LDAP modules).

johnbarclay’s picture

johnbarclay commented
Status: Active » Postponed (maintainer needs more info)
13rac1’s picture

13rac1 commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

Closing old issue, re-open if more information is available.