[webservices] restricted data

[John D. West]

Thanks, Philip! I'll check this out.

     -- John


On Fri, Oct 19, 2012 at 8:06 AM, Philip Crotwell <crotwell at seis.sc.edu>wrote:

> Hi John
>
> I have put up a tarball that handles the proxy for a dataselect style
> web service to a DHI seismogram server to allow access to restricted
> data. See the ReadMe in the tarball for how to use it.
>
> http://www.seis.sc.edu/~crotwell/dataselectDHIProxy/
>
> All a bit rough, but seems to work for my limited testing. Not bad for
> a couple of hours in the morning.
>
> You might want to look at bit at this to see how it is done in SOD,
> which is closely related to this code:
> http://www.seis.sc.edu/sod/documentation/restricted.html
>
> Enjoy, and let me know if you find any issues.
> Philip
>
> On Thu, Oct 18, 2012 at 6:00 PM, Chad Trabant <chad at iris.washington.edu>
> wrote:
> >
> > Hi Philip,
> >
> >> In the mean time, you can access restricted data with DHI. It would
> >> not be much of an effort to put a thin web services wrapper around the
> >> existing DHI seismogram server and to allow this now.
> >
> > My guess is we have different ideas of how much effort it would take.
>  Also, since DHI will be retired after Jun 30th next year it would be
> temporary at best.
> >
> >> Revamping restricted data access password sounds like a good idea. Old
> >> system was always a bit weird.
> >
> > Yeah, we think so too.  When the old system was started decades ago it
> was a pretty good fit for the problem, moving into DHI and then web
> services it's less convenient.
> >
> > Chad
> >
> >> Just my $0.02
> >> Philip
> >>
> >> On Wed, Oct 17, 2012 at 11:33 PM, Chad Trabant <
> chad at iris.washington.edu> wrote:
> >>>
> >>> Hi John,
> >>>
> >>> As a conservative estimate I would say that access to restricted data
> via web services should be in place in early next year.  I'm hopeful it'll
> be sooner but there are a lot of details involved.
> >>>
> >>> As a bit of insight into what we're doing: the DMC old (current)
> access was not a good fit for access via services, a password was specific
> to a data set and shared between researchers.  We needed a new paradigm in
> which a users' personal password will give them access to all the data sets
> they are allowed to access.  At the same time we modernized the internal
> password management at the DMC.  A message has been drafted explaining the
> details to those users with restricted data sets, but in short you'll be
> able to use the same data web services and provide a username and password
> to get access to your data.  HTTP Digest Authentication will be used, it's
> standard and well supported by nearly all HTTP clients/toolkits.
> >>>
> >>> Chad
> >>>
> >>>
> >>> ----- Original Message -----
> >>> From: "John D. West" <john.d.west at asu.edu>
> >>> To: "IRIS Web Services List" <webservices at iris.washington.edu>
> >>> Sent: Wednesday, October 17, 2012 2:21:39 PM
> >>> Subject: [webservices] restricted data
> >>>
> >>>
> >>> Greetings.
> >>>
> >>>
> >>> I'm getting questions about requesting restricted data through
> EMERALD. Do you have an estimate as to when that functionality will be
> available?
> >>>
> >>>
> >>> Thanks!
> >>>
> >>> -- John
> >>>
> >>> _______________________________________________
> >>> webservices mailing list
> >>> webservices at iris.washington.edu
> >>> http://www.iris.washington.edu/mailman/listinfo/webservices
> >>> _______________________________________________
> >>> webservices mailing list
> >>> webservices at iris.washington.edu
> >>> http://www.iris.washington.edu/mailman/listinfo/webservices
> >>
> >> _______________________________________________
> >> webservices mailing list
> >> webservices at iris.washington.edu
> >> http://www.iris.washington.edu/mailman/listinfo/webservices
> >
> >
> > _______________________________________________
> > webservices mailing list
> > webservices at iris.washington.edu
> > http://www.iris.washington.edu/mailman/listinfo/webservices
>
> _______________________________________________
> webservices mailing list
> webservices at iris.washington.edu
> http://www.iris.washington.edu/mailman/listinfo/webservices
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iris.washington.edu/pipermail/webservices/attachments/20121019/ea705179/attachment.htm>