Environment
Novell SecureLogin
NSL6.x
NSL7.x
SecureLogin installed in AD mode
NSL6.x
NSL7.x
SecureLogin installed in AD mode
Situation
Is it possible to force SecureLogin to access Active Directory through a specific domain controller?
Can SecureLogin be directed to use a certain AD server for all communication with the directory?
Can SecureLogin be directed to use a certain AD server for all communication with the directory?
Resolution
It is not possible to specify a specific server for NSL communication with AD.
SecureLogin uses ADSI (Active Directory Service Interfaces) to communicate with the AD domain, and ADSI selects the domain controller to be used for NSL communication. NSL uses the ADSI "serverless bind" feature which makes a connection to any available server in the domain. "Serverless bind" prevents code failures when a specified server is unavailable.
SecureLogin connects for each transaction with the directory and then disconnects. This means that each time NSL connects it might go to a different server as chosen by the ASDI interface. But for the duration of each connection/transaction NSL stay with just one DC. There is, however, no guarantee that a specific server will be selected
SecureLogin uses ADSI (Active Directory Service Interfaces) to communicate with the AD domain, and ADSI selects the domain controller to be used for NSL communication. NSL uses the ADSI "serverless bind" feature which makes a connection to any available server in the domain. "Serverless bind" prevents code failures when a specified server is unavailable.
SecureLogin connects for each transaction with the directory and then disconnects. This means that each time NSL connects it might go to a different server as chosen by the ASDI interface. But for the duration of each connection/transaction NSL stay with just one DC. There is, however, no guarantee that a specific server will be selected