Synergetic Windows Client (SynMain) and Azure AD: Solutions for Authentication Compatibility

The Synergetic Windows client, SynMain (a FAT32 application), relies on Kerberos authentication to communicate with on-premises domain controllers (DC). However, when end-user devices are Azure AD-joined, the SynMain client doesn’t function as expected. This is because Azure AD does not natively support Kerberos authentication.

Why Azure AD Does Not Support Kerberos Authentication

Azure AD is designed primarily for cloud-based authentication and does not include the traditional Kerberos protocol used by on-premises Active Directory (AD). Kerberos relies on a trusted third-party (the Key Distribution Center, or KDC) to issue tickets for authentication, which is a core component of on-prem AD environments. Azure AD, on the other hand, uses modern authentication protocols such as OAuth 2.0 and OpenID Connect, which are not compatible with Kerberos.

...

By implementing one of these solutions, you can ensure that the Synergetic Windows client (SynMain) continues to function as expected while leveraging the benefits of Azure AD and cloud services. If you need further assistance with any of these steps, please raise a new case through the help portal.

Troubleshooting

TBC