The solutions provided are described in isolation to each other. It's viable to have a combination of Connect for Chromebooks and SSL / non-SSL login pages for authentication:
If your Connect for Chromebooks solution uses Google verification, do the following to use SSL / non-SSL login pages as well:
Connect for Chromebooks uses HTTPS to communicate with Google's OAuth servers. This is suitable for SSL login pages, and you don't need to do any further configuration.
However, if you want to make use of non-SSL login pages (for authentication over HTTP), add the following to the web application you created in the Google API Console, see our knowledge base article, Where do I get the Client ID and Client Secret from for Google Authentication?:
Your web application's Restrictions should resemble:
Do the following to use SSL / non-SSL login pages:
WARNING: Be aware that by turning on Validate user identity, you're changing the behavior of the Connect for Chromebooks extension from trusting to verifying. We recommend that you make your end-users aware of this, especially as they must interact with the client login page as part of their authentication.
Note: The HTTP version doesn't need the port number.
If you don't have Connect for Chromebooks or SSL or non-SSL login authentication pages setup, we recommend that you configure Connect for Chromebooks using Google verification first, including setting up all additional configuration, then enable SSL or non-SSL login pages. This way, you've all relevant filtering policies in place first to catch any users who might browse while you're still setting up.
Something not right? Send us feedback.