Thanks, Philip! I'll check this out.<div><br clear="all"> -- John<br>
<br><br><div class="gmail_quote">On Fri, Oct 19, 2012 at 8:06 AM, Philip Crotwell <span dir="ltr"><<a href="mailto:crotwell@seis.sc.edu" target="_blank">crotwell@seis.sc.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi John<br>
<br>
I have put up a tarball that handles the proxy for a dataselect style<br>
web service to a DHI seismogram server to allow access to restricted<br>
data. See the ReadMe in the tarball for how to use it.<br>
<br>
<a href="http://www.seis.sc.edu/~crotwell/dataselectDHIProxy/" target="_blank">http://www.seis.sc.edu/~crotwell/dataselectDHIProxy/</a><br>
<br>
All a bit rough, but seems to work for my limited testing. Not bad for<br>
a couple of hours in the morning.<br>
<br>
You might want to look at bit at this to see how it is done in SOD,<br>
which is closely related to this code:<br>
<a href="http://www.seis.sc.edu/sod/documentation/restricted.html" target="_blank">http://www.seis.sc.edu/sod/documentation/restricted.html</a><br>
<br>
Enjoy, and let me know if you find any issues.<br>
<span class="HOEnZb"><font color="#888888">Philip<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Thu, Oct 18, 2012 at 6:00 PM, Chad Trabant <<a href="mailto:chad@iris.washington.edu">chad@iris.washington.edu</a>> wrote:<br>
><br>
> Hi Philip,<br>
><br>
>> In the mean time, you can access restricted data with DHI. It would<br>
>> not be much of an effort to put a thin web services wrapper around the<br>
>> existing DHI seismogram server and to allow this now.<br>
><br>
> 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.<br>
><br>
>> Revamping restricted data access password sounds like a good idea. Old<br>
>> system was always a bit weird.<br>
><br>
> 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.<br>
><br>
> Chad<br>
><br>
>> Just my $0.02<br>
>> Philip<br>
>><br>
>> On Wed, Oct 17, 2012 at 11:33 PM, Chad Trabant <<a href="mailto:chad@iris.washington.edu">chad@iris.washington.edu</a>> wrote:<br>
>>><br>
>>> Hi John,<br>
>>><br>
>>> 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.<br>
>>><br>
>>> 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.<br>
>>><br>
>>> Chad<br>
>>><br>
>>><br>
>>> ----- Original Message -----<br>
>>> From: "John D. West" <<a href="mailto:john.d.west@asu.edu">john.d.west@asu.edu</a>><br>
>>> To: "IRIS Web Services List" <<a href="mailto:webservices@iris.washington.edu">webservices@iris.washington.edu</a>><br>
>>> Sent: Wednesday, October 17, 2012 2:21:39 PM<br>
>>> Subject: [webservices] restricted data<br>
>>><br>
>>><br>
>>> Greetings.<br>
>>><br>
>>><br>
>>> I'm getting questions about requesting restricted data through EMERALD. Do you have an estimate as to when that functionality will be available?<br>
>>><br>
>>><br>
>>> Thanks!<br>
>>><br>
>>> -- John<br>
>>><br>
>>> _______________________________________________<br>
>>> webservices mailing list<br>
>>> <a href="mailto:webservices@iris.washington.edu">webservices@iris.washington.edu</a><br>
>>> <a href="http://www.iris.washington.edu/mailman/listinfo/webservices" target="_blank">http://www.iris.washington.edu/mailman/listinfo/webservices</a><br>
>>> _______________________________________________<br>
>>> webservices mailing list<br>
>>> <a href="mailto:webservices@iris.washington.edu">webservices@iris.washington.edu</a><br>
>>> <a href="http://www.iris.washington.edu/mailman/listinfo/webservices" target="_blank">http://www.iris.washington.edu/mailman/listinfo/webservices</a><br>
>><br>
>> _______________________________________________<br>
>> webservices mailing list<br>
>> <a href="mailto:webservices@iris.washington.edu">webservices@iris.washington.edu</a><br>
>> <a href="http://www.iris.washington.edu/mailman/listinfo/webservices" target="_blank">http://www.iris.washington.edu/mailman/listinfo/webservices</a><br>
><br>
><br>
> _______________________________________________<br>
> webservices mailing list<br>
> <a href="mailto:webservices@iris.washington.edu">webservices@iris.washington.edu</a><br>
> <a href="http://www.iris.washington.edu/mailman/listinfo/webservices" target="_blank">http://www.iris.washington.edu/mailman/listinfo/webservices</a><br>
<br>
_______________________________________________<br>
webservices mailing list<br>
<a href="mailto:webservices@iris.washington.edu">webservices@iris.washington.edu</a><br>
<a href="http://www.iris.washington.edu/mailman/listinfo/webservices" target="_blank">http://www.iris.washington.edu/mailman/listinfo/webservices</a><br>
</div></div></blockquote></div><br></div>