ad – Syncplify Developers Blog

Syncplify Devs
January 24, 2023

Syncplify Server! v6.0.11 released

Today we released Syncplify Server! v6.0.11; here’s what’s new and improved in this version.

Importance of this update: IMPORTANT

Fixed

The Windows version of the installer is now compatible with Windows 11 and Windows Server 2022 (we had to give up the “dark theme” of the installer because Win11 and Win2022 don’t support it, so don’t be surprised if this installer looks “light-colored”)
Some clients may cause an “unexpected EOF” false-positive during long file transfers, our software no longer falls for it now
Authentication of LDAP (Active Directory) user profiles now works as expected in WebClient!

Upgrading from v6.0.x is a simple and fairly automatic process: simply download the latest version from the official download page, and install it over the existing version, all of your settings and license will be kept.

If, instead, you’re upgrading from an older (v4/v5) version, you find the upgrade instructions in our knowledge base.

Thank you all for trusting our software with your secure file transfers!

Leave a comment InRelease Notes Syncplify Server! WebClient!

Syncplify Devs
June 30, 2021

Dropping Windows User/Group support

Syncplify.me Server! v1.0 was released back in Q1-2014. Since then, and all the way up to now, nobody (not a single one of our customers) has ever used profiles of type “Windows User” or “Windows Group”.

We have plenty of customers who rely on “Active Directory User” and/or “Active Directory Group” profiles, that’s obvious and expected, and the most common user profile is the so-called “Normal” user, which is a basic user profile saved in the software’s own internal database. But nobody has ever used the local operating system user profiles.

Therefore, given the security implications involved, the fact that with v6 we’re going fully cross-platform, and the fact that no one seems to even want to use this kind of profiles, we decided to drop them.

Syncplify Server! v6.0 will then feature the following user profile types:

Normal (local to the server, saved in Syncplify Server!’s own internal database)
LDAP User (which includes Active Directory)
LDAP Group (which includes Active Directory)

Later, probably with the release of v6.1, we will also add support for SAML2.0 user profiles.

Greatly simplified Active Directory (LDAP) integration

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 |&gt; 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…

Syncplify Developers Blog

Tag ad

Importance of this update: IMPORTANT

Fixed