Support for SAML 2.0 is fairly basic but well understood, but Google Workspace does not use a publicly accessible metadata URL for its X.509 certificate exchange. Instead, they download an XML file from the GWS admin console and upload it to the service provider's console, likely for security reasons. Bitfender only accepts public-facing metadata URLs as of today.
Implementing this wouldn't be difficult, as 95% of the SAML integration is similar to others. All you need to do is add an upload button for the metadata XML file or include extra fields for copying and pasting the metadata into GravityZone. I believe Bitwarden uses the string field approach, which worked quite well for us when we implemented it. Ideally, I think others will eventually move away from publicly accessible metadata URLs, and this "idea" will make sense for Bitdefender to implement.
Many schools and small businesses use Google Workspace, and this would benefit those users by reducing identity complexity and enhancing login security across their user base. Additionally, as Bitdefender releases more GWS products, SAML integration will become essential. I'm excited to collaborate with your team and hope this "idea" finds you well! At the very least, it offers GravityZone greater flexibility for its customer base. Let me know if I can assist in any way to make this happen!
Thanks much!
Mitch
