Hi, Muhammad. It's not clear what your intended use cases will be at the moment at all. Please describe what you need to achieve in more details. What protocols those users will use (OIDC, SAML, CAS etc), how will they interact with Gluu, in what exact case they will need to terminate their sessions, how do you see that should happen etc.

There are no API's you can call to discover this information. You'd have to build something custom to look at sessions LDAP. Also, note in version 3.1, session storage may be in Redis. Also keep in mind that even if you terminate a session in the OP, we don't support back channel logout. So the applications may not know that the session is over. Back channel logout support is also currently scheduled for version 3.1.