We had a couple of users write in this week, saying that they were having trouble re-authorizing Kerika for their Google Apps domain following our recent upgrade to OAuth 2.0.

In both cases, it turned out that the Google Apps Admin had previously authorized Kerika only for a subset of their Google Apps domains, i.e. for an Organizational Unit (OU).

Even when the OU has been set up to override the master settings of the domain, Google seems to be giving us an error (specifically, our server is told by Google’s authorization server that “domain policy checking failed” — this is the check that we do to see if the Google Apps domain is authorized.)

The simple fix is to authorize Kerika for the entire domain rather than a subset of users.

Naturally, our users wonder if this means they need to license all of the users registered within their entire Google Apps domain: the short answer is “No” — you need to license only those people who are actually using Kerika.

So, don’t worry about getting stuck with a big bill simply because you authorized the use of Kerika within a large Google Apps domain: all you are doing is making it easy for your colleagues to try out Kerika.

If they try out Kerika and like it, we can talk about licensing then…