In an environment where there are several Active Directory (AD) or ADLDS (ADAM) domain controllers and an ESSO controller on each one, technical definitions are lost in a scenario like the following one:
- start of SSOStudio
- creation of an application without windows and stop of SSOStudio
- there is AD or ADLDS replication
- start of SSOStudio
- creation of a "Standard Login" window for the previous application and stop SSOStudio
- start of SSOStudio: the "Standard Login" window is not visible : the Technical Definition is lost.
It is possible to force QESSO to always use the same controller or same ADLDS by forcing WGSS to always take the first server in the list if available.
Set to 1 the following registry value:
HKLM\SOFTWARE\Enatel\WiseGuard\FrameWork\Directory
FollowServerListOrder (DWORD)
It applies to all configurations which use a "ServerList" registry key (everything except AD).
The first server is always used unless it is not available, then the next is used unless it is not available.
Without the registry entry activated the list is randomly sorted at startup, and then it follows the same algorithm as above. If the server is available, we keep using the same one.
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center