For our customers running client-server applications on Windows, it is possible with 4D v15 R5 to enhance the end-user experience by using the Single Sign On feature, which basically allows your end-user logged into the system to also use their 4D application without being asked to re-enter any login/password.
To do so, 4D uses Windows technology that permits retrieving the user’s login connected to the current Windows session (using Active Directory). Once the login is known, the 4D application can determine by itself the rights assigned to this particular user.
The following command has been added to retrieve the Windows login.
$login := Current client authentication ( {$domain ;$protocol } )
$login: Windows ID used by the user to open his Windows session
$domain: Windows host domain
$protocol: Protocol used to make the authentication.
Two protocols can be used: NTLM or Kerberos. The best protocol is automatically selected by 4D depending on your architecture.
An “How DO I” example database is available:
For more details about SSO, please refer to the 4D v15 R5 Upgrade manual.
Integration to LDAP
This feature can also be combined with the LDAP feature (available since 4D v15) that allows you to retrieve information from LDAP servers such as Active Directory servers. You can see an overview with with this video: