Comment 9 for bug 978127

I see a couple of potential problems with the first approach:

 * There may not be a time-sync url (ntp service) available
 * Unless you're talking about adding an API call to MAAS? This obviously adds more complexity to the SRU.

The key thing is that the node clocks need to be "near enough" to the MAAS server's clock for oauth to work. We could just put the time right in the config payload but I guess that depends on whether having a more accurate clock time available for other purposes is desirable or not? If not, we can just make the config payload item be called "oauth_time_sync" instead so it's a bit more obvious what it's used for (and would discourage other use).