Saw this and just deployed a fix. It had previously required you to log in on the site first but it should automatically work now.