[Handle-info] accessing non-public values in client API (solved)

[Scott Yeadon <scott.yeadon@anu.edu.au>]

Hi,

I knew it was something simple - I had mucked up the AdminRecord index 
on the 0.NA/10378.1 HS_ADMIN value of 10378.1/2 and set it to 100 
instead of 200 (i.e. a lazy copy and paste error). Apologies for the 
noise (again!)

Scott.

Sean Reilly wrote:
> On Oct 16, 2008, at 12:30 AM, Scott Yeadon wrote:
> > Can anyone shed some light on what's happening here, it's probably 
> > something really obvious but I haven't been able to spot it looking 
> > through the logs and server code? Is anyone familiar enough with the 
> > code to state what the code is doing to satisfy itself a hidden value 
> > can be returned? (I was going to add some debugging to the 
> > HandleServer class but there are whole set of jars which don't appear 
> > to be part of the source distribution that throw errors when I run an 
> > ant build.)
>
> It sounds like the "read value" permission is not enabled in the 
> applicable HS_ADMIN records.  If you don't have that permission in the 
> handle then you won't be able to read any non-publicly-readable 
> values.  This applies even if there are no non-publicly-readable values.
>
> > As a secondary question (which could be related to the above 
> > problem), can I create a HS_ADMIN value which is self-referential 
> > i.e. the handle which the HS_ADMIN value is part of represents an 
> > admin-type user who has certain privileges on their own handle? See 
> > http://hdl.handle.net/10378.1/2 as an example.
>
> Yes, absolutely.  That is how most of our "user handles" at CNRI work.
>
> FYI: I get a "Cannot connect to server" error when trying to resolve 
> your example handle.
>
> Thanks,
> Sean


_______________________________________________
Handle-Info mailing list
Handle-Info@cnri.reston.va.us
http://www.handle.net/mailman/listinfo/handle-info