Troubleshooting Google Apps Migration for Microsoft Exchange – OAuth Authentication Failure

When trying to use the Google Apps Migration for Microsoft Exchange tool, I came across the following error:

Invalid Consumer Secret specified. Google Apps server has denied access to these credentials.

I checked and double-checked to make sure I had the correct OAuth Domain Key and Consumer Secret entered, and when it still failed, I re-generated the Consumer Secret.  Still no love.  After some searching, I came across this thread on Google’s Product Forums:

Invalid Consumer Secret

In a nutshell, when configuring your OAuth Domain Key, you have the option to “Allow Access to All API’s”.  For, me this box was checked.  Turns out when they say “All API’s”, they didn’t include some new ones that the latest version of the GAMME tool requires.  The tool looks for those API’s, can’t access them with the credentials you’ve supplied it, and falls on its face.  The fix involves you removing that checkmark next to “Allow Access to All API’s” and then heading to the “Manage Third-Party OAuth Client Access” page.  Type in your domain name into the “Client Name” field, and then paste the following into the “One or More API Scopes” field:

https://apps-apis.google.com/a/feeds/emailsettings/2.0/,
https://apps-apis.google.com/a/feeds/user/#readonly,
https://www.google.com/calendar/feeds/,
https://www.google.com/m8/feeds/,
https://www.googleapis.com/auth/apps.groups.migration,
https://apps-apis.google.com/a/feeds/migration/,
https://apps-apis.google.com/a/feeds/group/#readonly

Click the “Authorize” button, and that’s that.  Now the GAMME tool completes it’s diagnostic checks and will happily begin migrating the contents of your Exchange mailbox into Google Apps.

Attribution:  http://zerogb.wordpress.com/2013/07/12/troubleshooting-google-apps-migration-for-microsoft-exchange/

Annoying issue with * Stopping web server apache2 [Mon Feb 03 16:26:53 2014] [warn] _default_ VirtualHost overlap on port 443, the first has precedence ... waiting

To fix this issue just do this one, after which reload apache on the server

    # If you add NameVirtualHost *:443 here, you will also have to change
    # the VirtualHost statement in /etc/apache2/sites-available/default-ssl
    # to 
    # Server Name Indication for SSL named virtual hosts is currently not
    # supported by MSIE on Windows XP.

    NameVirtualHost *:443  # !important!
    Listen 443