sandbox.learningregistry.org now requires authentication

[Phil]

Hello,

The sanbox server was down for several day and is now back online. It appears that it now requires authentication to publish.

The command below shows a simple curl:
   curl -H 'Content-type: application/json'  -X POST -d @LearningRegTest_output.json http://sandbox.learningregistry.org/publish

Here are the results I get:
   {"message": "Basic Authorization Required", "OK": false}user1@VB-Ubuntu11:~/Documents/LearningRegistry$

LRSignature just flat out crashes with a stacktrace followed by:
   HTTP Error 401: Unauthorized

Where can I register for an account??

Thanks,
Phil

[Walt Grata]

Phil I can create an account for you, email me privately and I'll get you setup.

--
---
This message is posted from the Google Groups "LearningRegistry" group. More information about the Learning Registry project can be found at http://learningregistry.org/
 
To post: learning...@googlegroups.com
To unsubscribe: learningregist...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/learningregistry?hl=en?hl=en

[Jim Klo]

Hi, 

Walt's been in the process of deploying the next release onto sandbox.  Production will follow.

As part of this release, we are removing authentication from within NGINX - which will simplify security and make it more portable in the long term.

You will be able to use both basic auth and OAuth for publishing.  Using OAuth will allow you to publish and let the server sign your envelopes for you. Unfortunately, those of you with existing publishing accounts will need to recreate your account once deployed as the accounts were not transferrable from the old format to the new format.

Signup should be at:

http://sandbox.learningregistry.org/auth

Walt is still working out a few kinks in the rollout… Apologies for any inconvenience this may cause. If you come across more issues, please post to the dev list.

- Jim

Jim Klo

Senior Software Engineer

Center for Software Engineering

SRI International

t. @nsomnac

On Sep 6, 2012, at 11:06 AM, Phil <dune...@gmail.com>

 wrote:

[Walt Grata]

All issues appear to be worked out.  There was a problem caused by an update to the couchdb-browserid plugin, but Jim submitted a patch for the LR to fix the error.