When attempting to log into the Broadcom Security.cloud (ClientNet) portal or quanatine portal via Single Sign-On (SSO), users are redirected back to the login portal without being signed in. No explicit error message appears on the screen, but a browser network trace or SAML inspect tool reveals the following error query parameter:
error_description=Value+of+Identity+Subject+Claim:+'Email'+could+not+be+fetched+from+SAMLResponse
Email Security.Cloud integrated with Azure for SSO
This issue occurs because Microsoft Entra ID (Azure AD) appends a default URI namespace (e.g., http://schemas.xmlsoap.org/...) to the attribute names sent in the SAML assertion. Broadcom Security.cloud expects clean, case-sensitive attribute strings (like Email, FirstName, LastName) without any URL prefixes. Because of the namespace mismatch, Broadcom cannot find the required user identifiers.
Log in to the Microsoft Entra admin center.
Navigate to Identity > Applications > Enterprise applications.
Search for and select your Broadcom Security.cloud / Email Security.cloud application.
On the left menu, click Single sign-on.
Locate the Attributes & Claims section and click Edit.
You need to modify the claims so that they do not transmit a namespace prefix.
Click on the Email claim to edit it.
Locate the Namespace field and delete its contents entirely (leave it completely blank).
Note: Ensure the Name field is set exactly to Email and is not duplicated into the namespace.
Click Save.
Repeat this exact process for the FirstName and LastName claims:
Click the claim > Delete everything in the Namespace field > Click Save.
Once updated, your Additional claims table should display clean claim names without any URL prefixes or slashes, matching this layout:
| Claim Name | Namespace | Value |
| [Blank] | user.mail | |
| FirstName | [Blank] | user.givenname |
| LastName | [Blank] | user.surname |
Close your browser entirely or open a new Incognito/InPrivate window.
Navigate to your Broadcom Security.cloud portal login link.
Authenticate via Entra ID. The login should now succeed, routing you cleanly into the dashboard.