Troubleshooting Connect for Chromebooks
Article #: |
Product: |
Version: |
---|---|---|
# |
Connect for Chromebooks |
Glamis onwards |
Summary:
The following article aims to provide troubleshooting tips for the Connect for Chromebooks feature.
Full Description:
Connect for Chromebooks' Icons and Status
Connect for Chromebooks places an icon in the Chrome browser taskbar. It displays the extension and user authentication status as follows:
Status Icon |
Description |
|
The user is logged into Connect for Chromebooks, and browsing is allowed. |
|
Connect for Chromebooks is running but has an error. |
|
Connect for Chromebooks has an error. |
Clicking on the icon displays a pop-up window with a detailed description of the current status:
Status |
Description |
|
The user credentials of the logged in user are displayed. |
|
Connect for Chromebooks is unable to connect to the Internet to authenticate the user. |
|
There is a problem with Connect for Chromebooks. |
|
Connect for Chromebooks is busy. |
Connect for Chromebooks Log
Connect for Chromebooks provides a log of the user activity from the Chromebook it is installed on, namely which users have logged on, and the status of their login:
1. | From the Chromebook, click the Connect for Chromebooks icon. |
2. | From the pop-up window, click Diagnostics. |
Origin_Mismatch Error
This indicates the Smoothwall hostname does not match the one configured in the Google API console for the web application (Authorized JavaScript origins) — see Where do I get the Client ID and Client Secret from for Google authentication?
Ensure that the hostname configured is the Smoothwall appliance's fully qualified hostname, for example:
https://local.smoothwall.com:442
Tip: It should be noted that hostnames are case-sensitive so you must configure the Authorized JavaScript origins parameter to be exactly the same as the Smoothwall hostname.
Invalid_Client Error
If you are using Google verification with Connect for Chromebooks, you may find your users see this error in their Chrome browser when they click the red Google sign-in button.
This indicates that either the Client ID or Client Secret, or even both, that the Smoothwall is sending to Google for user verification purposes does not match those in the web application created in the Google API console — see Where do I get the Client ID and Client Secret from for Google authentication?
Log back into the Google API console, go to theCredentials page and copy the Client ID and Client Secret again.
Log back in the Smoothwall administration user interface, go to Services > Authentication > Google and re-enter the Client ID and Client Secret.
Unable to Determine a Proxy Server
Should Connect for Chromebooks be unable to determine a proxy server, or your network is configured for a transparent proxy method, an additional DNS entry should be added to your local DNS settings:
autodiscover.smoothwall.net
mapped to the internal IP address of the Smoothwall.
This is because Connect for Chromebooks uses the above domain name when attempting to communicate directly with the Smoothwall in the absence of a proxy setup.
My Network uses a Transparent Proxy Method
If you network uses a transparent proxy method, you should add the DNS entry detailed above.
Attribution:
Last updated: |
Author: |
Contributions by: |
---|---|---|
23rd November 2016 |
Samantha Nair |
|