SSO FAQs

No. Once enabled, you'll no longer be able to sign in to Portal using your existing Bazaarvoice password. Instead, enter your email on the SSO sign-in page. You will then be redirected to sign in via your IdP, before being brought back to the Bazaarvoice Portal.

When new users sign in to Portal using SSO, user accounts are created automatically using profile information from their IdP's default settings. If you assigned base permissions during setup, these will be applied to all new users within your domain.

Users should reach out to their CSM before changing their email address. When the user signs in using their new email address, a new user account will be created (using Just–in-Time provisioning). The user's previous permissions will be merged to the new account.

Yes. Federated users can be deleted manually from Portal. However, this is not recommended. Once a user is deleted, all audit history will be lost. Additionally, users who are deleted will be recreated the first time they sign in through their IdP. To completely remove a user, you must delete their IdP credentials.

SSO allows you to access Bazaarvoice solutions using your company's credentials. This means your Bazaarvoice account is now linked to your corporate IdP. As a result, there are some parts of your profile which cannot be edited in Portal, such as your name or password. Instead, you can update these parts of your profile in your corporate IdP account and your Bazaarvoice Portal account will be updated automatically.

From the upper-right corner, select the settings icon . Select Manage Users. Select your name to view your account details, access rights, and assigned roles. Note that you can only view this page as an Account Administrator.

If you're not assigned the Account Administrator role, sign in to Portal, go to your Profile page and select View Administrators to discover who can assign you this role.

No. We only support permissions for individual accounts.

Bazaarvoice only supports SAML protocol for FSSO.

Yes. To restrict access for a user, remove them from your Bazaarvoice IdP configuration.

No. Once SSO is set up for your instance, it applies to all of its users.

To change your domain(s), access the configuration details page by following the steps in the Edit SSO configuration section. Navigate to the Email domains section where a list of your domains will appear. To change a domain, select the trash can icon beside the domain you want to change and then select the Add domain link to add the updated domain.

To verify your domain(s), go to the Email domains section of your configuration setup. Bazaarvoice will provide you with a token which will allow you to create a .txt record . This should then be added to your domain's DNS settings. The length of time it takes to complete verification will depend on your domain provider.

No. However, if you delete one of your domains and need to re-add it at a later stage, you will need to generate the .txt record again.

No. Bazaarvoice doesn't share or accept any metadata files.

No. However, they will no longer be able to sign in to Portal even if they still have a Portal account.

Yes, through your own Identity Provider. Bazaarvoice supports Federated Single Sign-On (FSSO), and MFA enforcement is handled entirely within your IdP's policies, not by Bazaarvoice. See How Portal SSO and MFA work for details.

If you see this error message, contact your CSM.

If you can't see this tab, contact your CSM.

This could be due to one of the following reasons:

• If you are a new BV Portal user, it is possible that attribute mapping was not completed correctly during setup. This would stop JIT provisioning from functioning properly.
• If you are an existing user, it is possible that your SAML details do not match the details in your IdP. This may be because incorrect details were added during Step 3 or Step 4 of SSO setup.

Your user account needs to be set up manually. Your account administrator should check that all IdP credentials have been entered correctly during setup to prevent this happening for other users.

Tip: If JIT provisioning continues to fail, a temporary fix is to set up user accounts manually in the Bazaarvoice Portal. 

There are multiple reasons why you may be receiving this message:

• SAML details (ACS URL, Identity URL) details are incorrect, causing a conflict between BV and IdP details. Ensure the Identity URL, ACS URL and Audience URL match their equivalents in your IdP.
• The certificate uploaded in Step 3 of the wizard is invalid.

There are multiple reasons why this may be happening:

• If the user is new to Bazaarvoice and there is a mismatch in their SAML attributes between Bazaarvoice and your IdP, this causes JIT provisioning to fail. To fix this issue, make sure the attributes match up or ask Bazaarvoice to federate the user.
• If the user is an existing user, there may have been a change in IdP configurations. In this case, contact your CSM.

If you're unable to verify any of your domains, please contact Bazaarvoice Support, your CSM, or your TSM.

It depends on how you've signed in to Portal. If the email you've used to sign in matches an existing Portal account, the two accounts will be merged. However, signing in with a different email creates a new account whose base permissions are determined by your FSSO configuration. For example:

• If the email address for your account isportal-user@portal.bazaarvoice.com and you sign in using SAML and this same email address, you will sign in successfully to your existing account.
• If your account email address is portal-user@portal.bazaarvoice.com but you sign in using SAML with the email address portal@portal.bazaarvoice.com, a new account will be created for portal@portal.bazaarvoice.com that only gives you the base permissions you assigned when you set up your FSSO configuration.