Handle System Administration Tool

Welcome to the Handle System Administration Tool. This tool was developed for current users of CNRI's Handle System Server (HSj 5.2). The functions listed below allow authorized users (Administrators) to create, modify, and delete handles as well general users to resolve handles. The Help text can be accessed under each of the functions by pressing the Help button at the top of the active window.

Topics




Create Handle Help

Only authenticated users can create handles. Every handle MUST have at least one administrator. Every handle has a handle name and a group of handle values. Every handle value has an index, type, data, TTL(time to live), timestamp, permission set and references.

Steps:

  1. Input new handle name (NamingAuthority/LocalName)

    Type a new handle in the 'Handle Name' text box.Press 'Return'. This will check the authentication information, if left blank, an authentication box will pop up. The 'Change Authentication' button can be used to change the authentication information between handle creations.

    backto: Create Handle Help
  2. Input authentication information

    When an authentication box appears, choose secret or public key to authenticate. You must enter a handle, the handle value index and a secret key or private key file path in this box. Click 'Ok' to begin authenticaion or Click 'Cancel' to cancel it. When approving authentication, a pop up window will appear. If you want to interrupt the process, click 'Cancel' to interrupt the process. If the values entered are incorrect, an unsuccessful message will appear.

    backto: Create Handle Help
  3. Add Handle Data

    The 'Add Handle Data' box contains shortcut buttons for quick addition of certain handle types with defaults already set. The 'Add Custom' box is used to add handle values with custom types. Every handle value must have an index to identify it in the handle value group.

    backto: Create Handle Help
  4. HANDLE DATA VIEW

    This box displays the handle data values being added.

    backto: Create Handle Help
  5. Save and load

    backto: Create Handle Help
  6. Submit the created handle

    Press the 'Create Handle' button after the addition of all the handle values is complete. This will respond with an indication of success or failure. The absence of a administrator and handle name is considered a failure.

  7. Redo creation

    Redo all steps from entering the new handle name.

  8. Close

    Press the 'Close' button when the transaction has been completed.

    backto: Create Handle Help
Top


Modify Handle Help

Only authenticated users can edit handles, by adding, changing, and removing values. Every handle has a handle name and a group of handle values. Every handle value has an index, type, data, TTL(time to live), timestamp, permission and references.

Steps:

  1. Input handle name (NamingAuthority/LocalName)

    Type a handle in the 'Handle Name' text box.Pressing 'Return', will check the authentication information and fetch the handle values. If left blank, an authentication box will pop up. The 'Change Authentication' button can be used to change the authentication information.

    After authentication approval, all handle values will be displayed at the data list field. Without proper authentication only the 'public read' values will be displayed.

    backto: Modify Handle Help
  2. Input authentication information

    When an authentication box appears, choose secret key or public key to authenticate. You must enter a handle, the handle value index and a secret key or load private key in this box. Click 'OK' to begin authenticaion or Click 'CANCEL' to cancel it. When authenticationIS approved, a window will pop up, you could click its 'Cancel' to interrupt the process. If the values entered are incorrect, an unsuccessful message will appear.

    backto: Modify Handle Help
  3. Add Handle Data

    The 'Add Handle Data' box contains shortcut buttons for quick addition of certain handle types with defaults already set. The 'Add Custom' box is used to add handle values with custom types. Every handle value must have an index to identify it in the handle value group.

    The add value request will be sent to handle system.

    back to: Modify Handle Help
  4. HANDLE DATA VIEW

    This box displays the handle data values being added.

    back to: Modify Handle Help
  5. Save

    'SaveToFile' button will allow saving the handle values to a file

  6. Redo modification

    Redo all steps from entering the new handle name.

  7. Close

    Press the 'Close' button when the transaction has been completed.

    back to: Modify Handle Help
Top


Remove Handle Help

Only authenticated users can remove an existing handle.

Steps:

  1. Input handle name (NamingAuthority/LocalName)

    Type a new handle in the 'Handle Name' text box.By pressing 'Return', the authentication information is checked, if the text box is empty, you will need to enter the information. The 'Change Authentication' button can be used to change the authentication information.

    The handle values will be fetched and displayed in the List field.

    back to: Remove Handle Help
  2. Input authentication information

    When an authentication box appears, choose secret key or public key to authenticate. You must enter a handle, the handle value index and a secret key or load private key in this box. Click 'OK' to begin authentication or Click 'CANCEL' to cancel it. Click 'Cancel' to interrupt the process. If the values entered are incorrect, an unsuccessful message will appear.

    back to: Remove Handle Help
  3. Submit the removed handle

    Press the 'Remove Handle' button to confirm the remove operation. It will respond with an indication of success or failure.

  4. Redo remove handle

    Redo all steps from entering the handle name.

  5. Close

    Press the 'Close' button when the transaction has been completed.

    back to: Remove Handle Help
Top


Query Handle Help

Only authenticated users can query restricted handle values(non public read). Other users can query public read handle values. Users can query specific types of handle values or specific index handle values.

Steps:

  1. Input handle name (NamingAuthority/LocalName)

    Type a handle in the 'Handle Name' text box.

    back to: Query Handle Help
  2. Input authentication information

    'Authentication' button will display an authentication box. When the authentication box appears, choose secret key or public key to authenticate. You must enter a handle, the handle value index and a secret key or load private key in this box. Click 'OK' to begin authentication or Click 'CANCEL' to cancel it. Click 'Cancel' to interrupt the process. If the values entered are incorrect, an unsuccessful message will appear.

    back to: Query Handle Help
  3. Input query indexes

    Type the indexes of the handle values which you want to query in the 'Handle Index' text field. Use commas to separate multiple index values.

    back to: Query Handle Help
  4. Input query types

    Users could select one, more or all handle value types for query by highlighting the selected types in 'Handle Type' field.

    back to: Query Handle Help
  5. Input query properties

    'Certify' --

    'Certify Cache' --

    'Authoritative' --

    'Encrypt' --

    'Ignore Restricted Values' -- Unauthenticated users check this to ignore non-public read handle values. Authenticated users could check this off to get non-public read handle values.

    back to: Query Handle Help
  6. Display handle values

    'Handle Data' box displays the handle data values being queried. Highlight selected handle values from this list to display their content.

    back to: Query Handle Help
  7. Submit the query handle

    Press the 'Submit' button to process the query, a window with 'Cancel' button will pop up during processing. You could interrupt the query through the 'Cancel' button. An error message will pop up if the query failed.

  8. Redo query handle

    Redo all steps from entering the new handle name.

  9. Close

    Press the 'Close' button when the transaction has been completed.

    back to: Query Handle Help
Top


Batch Submission

Only authenticated users can submit batch files. Batch files need to follow the batch file format. Every batch file could include more than one kind of handle operation (CREATE/DELETE/ADD/REMOVE/MODIFY). Users can authenticate through the batch files or through the GUI tools.

Steps:

  1. Batch file formats

    Users need to create a batch file before using the batch submission tool. All batch files are general text format. One batch file could have more than one handle operation. The handle operations are: Create Handle, Delete Handle, Home/UNHome Naming Authority Handle, Add Handle Value, Remove Handle Value, Modify Handle Value, Authenticate User. Each operation has a different batch format.
    If you need to change authentication for subsequent batch operations, the new authentication information should be put before the batch block. You could authenticate during the batch submission, then you need not include the authentication information in the batch file.

    back to: Batch Handle Help
  2. Load Batch file


    Clicking 'Add' button to enter the batch file path. This will be added to the batch file list window. You also could put all batch file paths in a list file and use 'LoadfromFile' to load and add to the batch file list window. The 'SavetoFile' allows you to save all file paths in the file list window into a file for future reference.

    back to: Batch Handle Help
  3. Authenticate


    There are 2 ways to authenticate: via the tool or from the batch file. See Authentication Information format above.

    back to: Batch Handle Help
  4. Submit Batch


    Click the 'Submit Batch' button to submit the batch operation.

    back to: Batch Handle Help
  5. Log files


    There will be output from the batch operation. To save successful messages to your specified Succ Log File and error messages to your specified Error Log File, you must check 'Save Log File' or the messages will go to stderr.

    back to: Batch Handle Help
Top


"Homing" a Naming Authority

"Homing" a naming authority on a particular site tells the server(s) that make up the site that they are responsible for the given naming authority. This way, when a resolver comes along and asks for a handle under that naming authority, the server can say "here it is" or "it doesn't exist" or even "Why are you asking me? I don't have it."

If you enter the naming authority handle as well as the address and port number of one of the primary servers for the desired site, this tool will "home" the given naming authority to that site. A message will be sent to each server in the site indicating that that site will now be responsible for the given naming authority. From then on that server will accept and handle requests for the given naming authority.

Top


"Unhoming" a Naming Authority

"Un-homing" a naming authority on a particular site tells the server(s) that make up the site that they are no longer responsible for the given naming authority, and that they should behave accordingly.

If you enter the naming authority handle as well as the address and port number of one of the primary servers for the desired site, this tool will "unhome" the given naming authority on that site. A message will be sent to each server in the site indicating that that site will no longer be responsible for the given naming authority. From then on that server will reject requests for the handles under the given naming authority.

Top


List Handles Help

The "List Handles" function of the admin tool sends a request to a service to list all of the handles for a specific naming authority. The administrator must have the "List Handles" permission enabled in the naming authority handle. The List Handles function is implemented in the most recent CNRI handle server, but if your handle database is very large, the list handles command may time out, since the database used by the CNRI handle server is not optimized for this kind of operation.

Top


Checkpoint and Recovery Help

The Backup Server function of the admin tool sends a request to a server to checkpoint its internal handle database. To perform a checkpoint, the administrator must be identified as an administrator for that server in the server_admins section of the config.dct file.

The checkpoint operation has two steps. Upon receipt of an authenticated request to backup the database, the server will:

  1. Copy the main database files (handles.jdb and nas.jdb) to backup files (handles.bak and nas.bak)
  2. Reset the transaction log (dbtxns.log)

The handles.bak and nas.bak files can be safely copied to another location for storage. The dbtxns.log file will contain all of the changes made to the database since the handles.bak and nas.bak files were made. The dbtxns.log file will allow you to restore the database from the backup up, to the last transaction that was successfully performed.

To begin the checkpointing process, enter the IP address and port number of the server. Note: During the checkpoint process, the server will reject all requests to create, modify, or delete handles. Perform the checkpoint operation when there is little administrative activity. Checkpoint operations should only be performed on primary servers. Secondary servers do not keep transaction logs for their databases.

To recover the database using the backup files and transaction log, perform the following steps:

  1. Ensure that the server is NOT running.
  2. If possible, make extra copies of all files.
  3. Run the command:
    java -cp handle.jar net.handle.server.RecoverJDB  <server_dir>
  4. Restart the server. The database should be restored to it's pre-disaster state.

Top


Session Setup Help

Using a Session reduces the authentication processing time for performing a sequence of administrative operations. Sessions also enable encrypting transactions between the client and hosting server.

Authenticated users establish a session with a server by selecting the "Use Session" option, generating (or using an existing) exchange key pair, and setting session attributes using the Session Setup panel.

Steps:

  1. Click the "Use Session" checkbox

    Check the "Use Session" checkbox to enable the session parameter entries. Each user explicitly sets session setup options via this panel.

  2. Click the "Use Server RSA Key" checkbox

    Check the "Use Server RSA Key" checkbox to use the server's RSA keys for the session exchange keys. (Ensure that the server has a pair of RSA keys before selecting this option.) This is the default setting.

  3. Specify exchange keys by generating RSA keys

    A server must have a pair of RSA keys in order to exchange a session key with the client. A client that wants to use its own RSA keys must uncheck the "Use Server RSA Key" checkbox, and then click the "Generate Key Pair" button to generate a new pair of RSA keys. When the "Generate Key Pair:" window comes up, choose "RSA" and click "GenKeys". After the keys are generated, close the "Generate Key Pair" window. The two key file names will be populate the "Public key file" and "Private exchange key file" fields.

  4. Specify exchange keys from existing RSA keys

    A server must have a pair of RSA keys in order to exchange a session key with the client. If a client wants to use its own RSA keys, and a pair of RSA keys has already been generated, uncheck the "Use Server RDA Key" checkbox, and specify the public key using one the following methods, and specify the private key in the 'Private Exchange Key File' field.

  5. Specify session options

    These controls are for specifying session options.

  6.  

  7. 'OK' session setup information

    Click the 'Ok' button to save your session setup information. All the parameters will be validated, and error messages will be displayed. Your new parameters for the session will take effect when your next administrative operation is executed.

  8. 'Cancel' session setup information

    Click the 'Cancel' button to cancel the session setup changes.

Top



hdladmin@cnri.reston.va.us