A small group of users sharing a single Apps10 login sometimes get a warning that someone else is using that login, but other times get silently logged out with lost work instead, with no consistent notification. Is there a way to make that notification reliable, or a better approach entirely?

All FAQ questions / Security and access

Answer

Rather than trying to make the shared-login collision notification more reliable, the real fix is to stop sharing a single login among multiple users — purchase individual LTU (Limited Task User) licenses for each person instead. IFS's licensing and session model isn't built around multiple people sharing one login concurrently, which is exactly why the collision-handling behavior (sometimes warning, sometimes silently kicking the other session) is inconsistent; separate named LTU accounts for each user avoids the problem at its source rather than trying to work around unreliable collision-notification behavior.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Security and access questions