Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Sign-in via Single Sign-On (SSO) in Socialcast displays the error: Email has already been taken (2036730)

Symptoms

  • Attempting to access the Socialcast community fails with error:

    Sign In required to view this page. Email has already been taken

  • When searching for a user in the Admin interface using an e-mail address, an active or de-activated account is found.

Cause

With SSO, the Company Login field is used as the unique identifier for users, not the e-mail address. When completing a sign-on using SSO, a user profile is searched for by looking for a match on the Company Login information first (using the identifier in the SAML Subject of the SSO Assertion), and then by e-mail address if a match is not already found.

When a match is found based on Company Login, the account is updated with the e-mail address and the names being passed via SSO. When updating, if the e-mail address of the matched user account is already in use by another account, the above error is displayed as e-mail addresses are required to be distinct for all accounts.

Resolution

To resolve this issue, the data being provided to Socialcast for the user's account must be accurate. The following checks should be performed.

  1. Verify the field mappings for SSO and LDAP. For more information, see Using SSO in combination with LDAP integration in Socialcast (2035371).
  2. Ensure e-mail addresses and usernames/identifiers are both unique in the set of users being generated by your LDAP integration.
  3. Perform another Directory Mirroring task (LDAP sync).
After this verification is complete, conduct another search for an active or deactivated user using the user's e-mail address. Once found, edit the user account and ensure that the Company Login username is updated manually to the correct value.

If the account being updated is currently deactivated in Socialcast, it is re-enabled when the user completes the next sign-in via SSO. If the error persists, then the unique identifier being passed in the assertion should be verified as it may not be the same information being passed via LDAP integration for Company Login or it may not be configured correctly and is using the same identifier for all users.

Note: For information on setting the correct identifier for Active Directory Federation Services 2.0, please refer to  Configuring an Active Directory Federation Services Relying Party for use with Socialcast Single Sign On (2035246).

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 0 Ratings
Actions
KB: