In order to more effectively implement authentication for the SDS (and protect the data and resources it contains) I am changing the name of the <user> resource in the SDS to <sail-user> in development sds today.
I never should have used the name user for a sail-user. I knew it was stupid when I did it ages ago and it was just laziness. Now that we have both a dev sds and a production sds I'm making these changes to the dev version at: http://rails.dev.concord.org/sds It's very likely that the dev sds will be unstable today. When these and many other changes in the dev sds have been tested they will be moved to the production sds at: http://saildataservice.concord.org When the dev SDS is stable again shortly you will need to authenticate before you can create or edit SDS resources. In addition shortly thereafter in order to do the same thing from a REST interface you'll need to use HTTP Basic authentication and probably connect via https to the SDS. At this point a browser starting a jnlp and interactions between the SAIL application and the SDS will not require HTTPS or authentication however that should be done soon also. Before the changes to the dev SDS are moved to the production SDS Cynic (PAS-Portal), Hiroki (DevWise), and CC (all the DIY variants) will need to make sure that their web applications will work with the new resource name. Aaron and I will be sending out more information about the plan for the rest of the changes soon. -- - Stephen Bannasch Concord Consortium, http://www.concord.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
