Tag samaccountname

More good news regarding Syncplify Server! version 6.0: we have greatly simplified the management of users (and even groups) profiles.

In all previous versions the Admin had to specify the type of LDAP query (UPN/sAMAccountName) and the desired order in case of multiple query types, but groups would only allow the use of UPNs; this, occasionally, led to some confusion.

As of version 6.0, Syncplify Server! is capable of gracefully handling both UPN and sAMAccountName logins, for both LDAP user and group profiles, no questions asked, no special configuration needed.

What you see in the picture here above is the same user, logging in twice, the first time using their UPN, and then using their sAMAccountName.

But wait… there’s more!

In the example above, what you see is not a user profile in Syncplify Server!… it’s an LDAP Group profile! The “sftptest” (or “sftptest@ad9.local”) user was able to log in simply because it’s part of the “sftpusers” LDAP group in the underlying Active Directory. And the session logs make it very clear:

nodeId="peaceful-booth"
sender="ssh2_sftp-handler"
sessionId="e6G8PrHp2KRjQrqCS3SDSn"
clientIp="127.0.0.1"
serverIp="127.0.0.1"
serverPort=22 
protocol="ssh2_sftp"
username="sftptest@ad9.local |> sftpusers"
method="SESSION-START"
uriStem=""
uriQuery=""
status=200
cliToSrvBytes=0
srvToCliBytes=0
latencyMillisec=0
latencyHuman="4.197µs"
userAgent="SSH-2.0-OpenSSH_8.4p1 Ubuntu-5ubuntu1"

This user profile simultaneously represents the user itself, as well as the group profile it belongs to, and from which it inherits its configuration, permissions, virtual folders, etc…