The issue is caused by the User-Agent, and how the SAML auth is handled. When you use SAML, the authentication is done through browser and after that the session cookie is transferred to the PDC. During the first authentication you will see: Login succeeded for "user/realm" from <ip-addr> with Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko. and then: Agent login succeeded for "user/realm" (session:xxxxxxx) from <ip-addr> with Pulse-Secure/9.x.x.xxx (Windows 10) Pulse/9.x.x.xxxx. That's not causing any warning, but when you have to extend the session, as you said you have to authenticate again while still having an active session. When you perform the re-authentication for extend the session, the PCS already has an active session with a different User-Agent, hence the warning. When using the AD you don't see any warning because the User-Agent is only one. I don't see any solution for this issue. Well.. a sort of solution could be enable more than 1 user session at realm level...
... View more