Modifying Enigma Timeout - ACS Level dependent

BBS Corner Area Enigma 1/2 BBS Software
1

If you’re a sysop testing out your Enigma 1/2 BBS Install, you’re probably like me where that idle timer timeout just comes too quick. While you can adjust it in your CONFIG.HJSON file, reading at face value, it appears to apply to all users.

But like a lot of the configurable options within Enigma, your timeout can also be ACS driven; not specifically mentioned in the documentation, so may not be easily apparent.

ACS Background as listed in Enigma Documentation:

" SysOp’s are able to control access to various areas of the system based on various conditions such as group membership, connection type, etc. Various touch points in the system are configured to allow for acs checks. In some cases ACS is a simple boolean check while others (via ACS blocks) allow to define what conditions must be true for certain rights such as read and write (though others exist as well)."

Default statement after building an ENIGMA 1/2 Configuration as found in CONFIG.HJSON:

    //  How long authenticated users (logged in) can idle
    idleLogoutSeconds: 360

The key is in the document section of ACS privileges. It lists “touch points” as follows:

image
image860×267 45.1 KB

so for the idleLogoutSeconds parameter, I modified the default to:

  //  How long authenticated users (logged in) can idle
  idleLogoutSeconds: [
  	{
  		acs: GM[sysops,co-ops]
  		idleLogoutSeconds: 9999
  	}
  	{
  		idleLogoutSeconds: 360
  	}
  ]

Boom - My all-powerful SYSOP privileges now bypass the 360 seconds and it works like a champ.
So consider other ACS levels that you might want to modify. Power Userz? Abuserz? Maybe something if it’s Bryan Ashby himself? (and if so, what would it be?? LOL)

Enjoy!
~-Nuke-~