Re: [Handle-info] Attempting to setup a Local server

[Sean Reilly <sreilly@cnri.reston.va.us>]

Hi Elliot,

My responses are below...


On Jun 27, 2006, at 10:32 PM, Elliot Metsger wrote:

> Hi Everyone,
>
> I looked in the archives but they were pretty lean so here's my  
> question.
>
> I'm using Sun Java 1.4.2 on Linux Handle 6.2, and I'm trying to get  
> my Handle Server running locally without contacting the Local  
> Registry.

I'm assuming this is just for testing/setup purposes.  If you  
actually use handles then you will need to acquire a prefix that is  
registered with the root/global system.  I believe that is part of  
the service agreement or license for the handle software.

> Here's what I did:
> 1. Went through the Simple Setup.
>
> Performed the required client side steps
> 2. Copied siteinfo.bin to ~/.handle/resolver_site
> 3. Created ~/.handle/local_nas with a single entry in it: "0.NA/1234"
>
> The client side setup seems to work.  Based on the output from the  
> Handle Tool it seems that all messages are being sent to my local  
> handle server.
>
> Performed the required servers side steps
> 4. Modified the config.dct file (question: do these parameters sit  
> inside the server_config = { ... } block, or do they sit by  
> themselves in the main body of the config file?  I've tried both.)

They should be inside the server_config block.

> 5. Fired up DB Tool and added the Naming Authority "0.NA/1234"
>
> 6. Used DB Tool to add the Handle "1234/ADMIN", with a data of  
> "admin".  Relative TTL of 86400 and (well, this is odd to me) a  
> timestamp of Monday Jan 05 07:15:57 EST 1970.  Checked permissions  
> are AR, PR, and AW.  PW is unchecked.  The Refs box is empty.
>    Here are all the parameters -
>    + index=300
>    + type=HS_ADMIN
>    + rwr-
>    + "admin"

Instead of HS_ADMIN you will need to set the type to "HS_SECKEY" and  
use "admin" as the secret key (password) when authenticating.  Values  
with type "HS_ADMIN" are contained in handles in order to specify who  
can modify them.  In this case the 1234/ADMIN handle is only being  
used to identify a single administrator.

> I can sucessfully list the naming authority and the 1234/ADMIN  
> handle using DB Tool.
>
> 7. Edited config.dct and replaced each occurance of "0.NA/ADMIN"  
> with "0.NA/1234/ADMIN".

That should be "1234/ADMIN".  All handles that begin with "0." are  
only located on the root/global servers.  By adding the 0.NA/1234  
prefix handle to your server you are telling the server that it is  
responsible for handles under the 1234/ namespace.

> I can start the handle server.  Then I start the Handle Admin Tool.
>
> I can click on the Handle Tool "Setup" button, then select  
> "Authentication".  I Authenticate using a secret key ("admin") with  
> an ID handle of "1234/ADMIN", and an ID Index of 300.  After  
> authenticating, I see "HS_SECKEY 1234/ADMIN:300" displayed at the  
> bottom of the Handle Tool.
>
> So far so good.  I can tell that the Handle authentication request  
> was sent to my local server:
> sending HDL-TCP request (version=2.1; oc=201; rc=0; snId=0 crt  
> caCrt noAuth 1234/ADMIN) to 128.220.8.104:2641
>     received HDL-TCP response: version=2.1; oc=201; rc=1; snId=0  
> crt caCrt noAuth
>
> So I try adding a handle by clicking on the "Create Handle" button  
> in the Handle Admin Tool.  I attempt to create the following handle:
> Handle: 1234/testfoo
> Handle Data View:
> index=100 type=HS_ADMIN Admin ID Handle: 1234/ADMIN Admin ID Index:  
> 300
> index=1 type=URL
>
> When I try to create it I receive the error:
> Response: Handle Creation Failed Error(400): INVALID ADMIN
>
> Handle Tool Output is:
> sending HDL-TCP request (version=2.1; oc=100; rc=0; snId=0 caCrt  
> noAuth adm 1234/testfoo) to 128.220.8.104:2641
>     received HDL-TCP response: version=2.1; oc=100; rc=402; snId=3  
> caCrt noAuth
>   sending HDL-TCP request (version=2.1; oc=200; rc=0; snId=3 caCrt  
> noAuth / HS_SECKEY 300:1234/ADMIN) to 128.220.8.104:2641
>     received HDL-TCP response: Error(400): INVALID ADMIN
>
> Any idea what I'm doing wrong?

Yes, this is the expected result if step 6 has the wrong handle value  
type.  I think that changing that will solve the problem, but please  
let me know if it doesn't!

Thanks,
Sean



--
Sean Reilly	CNRI/Reilly Technologies
Location this week:  Edinburgh, Scotland
hdl:200/0



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