33.7.3 Users Fail to Authenticate to MobileAccess when Appmarks Are Launched in the Chrome Browser

Issue: If a user sets up a Chrome profile and then tries to use a Google Apps resource configured to use Chrome on MobileAccess, the login fails because Chrome passes the saved profile user name and password to the resource instead of passing the user name and password from MobileAccess. This issue occurs for any Google Apps resource (for example, Gmail or Google Drive) on iOS and Android mobile devices. (Bug 948622)

Solution: Users can remove their Chrome profile to avoid this issue, or you can configure the appropriate Google Apps appmarks in Access Manager so the resources open with Firefox, an internal viewer, or a user-selectable option, instead of Chrome.