We ran into an issue on Friday with the Mozilla Persona / BrowserID implementation on Node01, which may have something to do with the OpenSSL update we applied last week after the HeartBleed vulnerability was reported. We're still looking into the the cause of the issue, but at this time I do not have a timeframe for when a fix will be applied.
If you would like to publish using the API you can continue to use Node02, even if you haven't registered for an account before (
https://node02.public.learningregistry.net/apps/oauth-key-management/). The BrowserID implementation on that node appears to be unaffected by this glitch. If the problem persists, we may install EasyPublish on Node02 as well (it's not currently) so that avenue is available to you again.
-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-
joe hobson, director of technology & innovation
Navigation North Learning