Hello Everyone,

In my VM environment, I have integrated multiple federated directories with ISVA. Any of these entries from the LDAP.conf file, when I put the following lines 
(ignore-if-down = yes) It removes automatically from the WebSEAL appliance LDAP.conf file, but its runtime does not starts it goes down. However, if I put this is at comment #ignore-if-down = yes, it is not removed 
even other attributes are unchanged 

[server:XXCORP]
host = XXXX.XXXX.X.
port = 389
bind-dn = CN=xxxx,OU=xxxx,DC=xxx,DC=xxxx (correct bind dn)
ssl-enabled = no
suffix = dc=xxx,dc=xxx
#ignore-if-down = yes
basic-user-principal-attribute = userPrincipalName

What can be the reason for this 

Thanks & Regards 

Hello Shivsantosh ,

Can you please let us know IVIA version ?

ignore-if-down is optional configuration entry controls whether Verify Identity Access will continue to operate using the other configured federated registries
if this user registry becomes unavailable.

Note: If this option is set to yes, Duplicate user ID detection is not permitted and must be disabled.  

This value cannot be set for the primary registry as failures on the primary registry cannot be ignored. If the configuration entry is not
set it will default to 'no'.

Hello Everyone,

In my VM environment, I have integrated multiple federated directories with ISVA. Any of these entries from the LDAP.conf file, when I put the following lines 
(ignore-if-down = yes) It removes automatically from the WebSEAL appliance LDAP.conf file, but its runtime does not starts it goes down. However, if I put this is at comment #ignore-if-down = yes, it is not removed 
even other attributes are unchanged 

[server:XXCORP]
host = XXXX.XXXX.X.
port = 389
bind-dn = CN=xxxx,OU=xxxx,DC=xxx,DC=xxxx (correct bind dn)
ssl-enabled = no
suffix = dc=xxx,dc=xxx
#ignore-if-down = yes
basic-user-principal-attribute = userPrincipalName

What can be the reason for this 

Thanks & Regards