Troubleshooting

Bad Request – Header Field Too Long

When logging in to  Haivision Hub using the FireFox browser, you might encounter an error: Bad Request – Header Field Too Long

This is due to exceeding the limit of the the number of cookies set by the login server.

Firefox

To resolve this issue:

1. Open the Manage Cookies and Site Data window in your FireFox preferences.

2. Delete the cookies associated with the site haivisionb2c.b2clogin.com.

Chrome

You can remove a specific website cookie from Chrome by doing the following:

1. Open Chrome if you have not done so already.

2. In the Chrome menu, select Preferences to open chrome://settings as a URL.

3. Scroll down and choose Show Advanced Settings, then go to the Privacy section and choose Content Settings…

4. Under the Cookies section, click All cookies and site data…

5. Locate the site cookie(s) associated with haivisionb2c.b2clogin.com, then click the (X) button to delete cookies.

6. When finished, click Done.

Approval Required

When logging in to  Haivision Hub using Azure Active Directory (AD), you may encounter an “Approval Required” prompt.

This is due to a policy setting in your organization's deployment of the Azure Active Directory. Consequently, approval from your organization's network administrator is needed to authorize Haivision Hub as a client and allow single sign-on with your Azure AD account. Since Haivision Hub doesn't request any internal access beyond basic identity verification, approving Haivision Hub to use AD authentication is a relatively easy and low-risk task for your network administrator. 

Tip

While the decision is up to your organization's IT administrators, Haivision recommends enabling all users of your Azure AD to authenticate to Haivision Hub . This will make it easier for you to grant new users access to Haivision Hub and eliminate the need for your IT organization to grant authorization for each user individually.

The first time a user with an Azure account tries to log in, Haivision Hub requests information from your organization’s AD authentication service.

We typically recommend customers use their SSO credentials that they normally use for their organization. The Azure AD warning seems ominous, but Haivision Hub doesn’t actually collect anything significant from your AD. Haivision Hub does need to know the users’ email addresses and display names. Using Azure B2c with the MS Graph API, we are requesting the lowest level of permission that grants us email address: User.ReadBasic.All. From the Microsoft Graph API Permissions Reference:

The User.ReadBasic.All permission constrains app access to a limited set of properties known as the basic profile. This is because the full profile might contain sensitive directory information. The basic profile includes only the following properties:

• displayName

• givenName

• mail

• photo

• surname

• userPrincipalName

For more information, refer to these Microsoft articles on Azure AD user consent workflows:

• Configuring User Consent

• Managing Consent Requests

• Granting Admin Consent

• Configuring Admin Consent Workflow

Duplicate Paired Device Names

Currently, devices cannot be renamed from the HUB , nor are changes in the device's name after pairing reflected in the HUB . Consequently, it is possible for multiple devices to be paired with the same name.

The workaround is to:

4. Unpair the device. See Unpairing an Appliance.

5. Rename it on the device's interface (e.g., Admin > Network tab > General section > Hostname 

   

   .

   

6. Pair  the device again to HUB . See Pairing an Appliance.

   

   The new name will be reflected in the listings.