Michel's question about login session TTL.

[support200]

We have a question regarding NXFilter. The server is configured with a session TTL of 10 hours (600 minutes); however, some users leave their machines on all day and only resume work the following day. This exceeds the 10-hour limit, which triggers a request for re-authentication. In this environment, NXMapper is active, and there is synchronization with Active Directory. Our question is: can NXFilter detect that the session has expired and renew it automatically, or does session renewal only occur upon the next machine login?
Could you please explain how this session TTL mechanism works?

[support200]

NxFilter refreshes a user's session when it gets a DNS request from them. As long as there is internet activity, the session doesn't expire. However, you'd better use an SSO agent like CxLogon if you don't want your users to go through the login page.

[support200]

Maybe you should have a default user linking the IP range covers whole network. Then when your users are not detected by any SSO agent, they will appear with the default username. And then when your SSO agent starts working then they will appear with the detected usernames.

[Michel Rodrigues 4infra]

I will check the feasibility of using `cxlogon` instead of `nxmapper`. Can `cxlogon` refresh the session periodically, or does the user need to initiate a DNS request?

[support200]

You take it in a wrong way. Leave NxMapper working. And then have a default user. If the network has 192.168.0.1 ~ 192.168.0.255, create a user named 'default' and link the IP range to the user. Then they will not see the login page. You may want to assign a policy having minimum permission to the default user.

You also can use CxLogon with NxMapper. CxLogon talks to NxFilter once in a minute. In an AD environment it will detect the same username as NxMapper. Actually these days, CxLogon is the default option as it works with or without Active Directory.

[Michel Rodrigues 4infra]

You take it in a wrong way. Leave NxMapper working. And then have a default user. If the network has 192.168.0.1 ~ 192.168.0.255, create a user named 'default' and link the IP range to the user. Then they will not see the login page. You may want to assign a policy having minimum permission to the default user.

You also can use CxLogon with NxMapper. CxLogon talks to NxFilter once in a minute. In an AD environment it will detect the same username as NxMapper. Actually these days, CxLogon is the default option as it works with or without Active Directory.

Alright, I will run the tests and let you know if the solution worked.