Returning Session and/or Idle timeout in a RADIUS Scenario.

Last modified on 21 Jan, 2021. Revision 6
This might be a requirement when setting up EasyAccess. Since we normally deal with users who uses NPS (Microsoft Network Policy Server) as RADIUS Server where Session and Idle timeout values are sent per default in the RADIUS ACCESS-ACCEPT. In EasyAccess these values are not sent per default and you have to manually specify that those should be returned. Here is how you do that.
Up to date for
EasyAccess 3.2.0
Status OK



Configuring EasyAccess

Go t your RADIUS Scenario under Scenario → Radius in the webui. Go to the “Execution flow” tab and add two PropertyAddVavles with the following configuration:

PropertyAddValve

{
        "name": "PropertyAddValve",
        "config": { 
              "name":"session",
              "value":"30",
              "splitter" : ";"
        }
}

PropertyAddValve

{
        "name": "PropertyAddValve",
        "config": { 
              "name":"idle",
              "value":"30",
              "splitter" : ";"
        }
}




Next go to the Advanced Tab and add the following under Response Attributes:

Related articles

Sending EasyAccess logs to InCenter or a Syslog server
4 May, 2021 easyaccess incenter syslog
Missing fonts when installing EasyAccess 4.0.2
30 Mar, 2021 linux easyaccess
How to disable OneTouch or OTP for specific users on RADIUS Authenticators.
24 Feb, 2021 easyaccess radius
How to configure passwordless OneTouch authentication
24 Feb, 2021 easyaccess radius saml sso onetouch
How do I work with nested groups (AD) in EasyAccess
21 Jan, 2021 easyaccess
Changing EasyAccess MyApps icons through the WebUI
18 May, 2021 easyaccess myapps
High Severity vulnerability in Apache Log4J 2
14 Dec, 2021 easyaccess log4j
How to import and enroll Feitian Hardware Keys (HOTP)
18 Jan, 2021 easyaccess hotp
Radius vs LDAP for authentication
21 Nov, 2022 radius ldap authentication core



Tagseasyaccessradius