User Registration Guide

You can browse the public content of a registry. However, both access to private objects and write access to public objects require that you are logged in and are authorized to perform that action on that object. Please see the User Registration Guide for an overview.

You must register with a registry before you can log-on to that registry and perform secure operations such as object publishing, update and removal. After registration, you will load your client certificate into your web browser. This allows the Registry to identify and authenticate you.

Registration using Registry Browser Web UI involves the following steps:

  1. Creating a User Account
  2. Loading Client Certificate into the Web Browser
  3. Loading Client Certificate to JAXR provider (optional)

After that you are able to authenticate with the registry.

1. Creating a User Account

  1. Browse to Registry Browser Web UI welcome page
  2. Click the 'Create User Account' on the left side menu
  3. Click the 'Start Registration Wizard' button
  4. Step 1: Read the requirements and click 'Next' button
  5. Step 2: Fill in the user details. Notice that first and last name are required. Click 'Next' button to continue.
  6. Step 3: Fill in the user authentication details. Unless you already have a CA certified digital private key, you should choose 'Generate Key pair and download PKCS12 KeyStore'. Important: remember the password you write here. It will be needed to import the certificate on a later step. Click 'Next' button to continue.
  7. Step 4: click the 'Download' link and save the certificate file in your computer.
  8. Click 'Finish' button to end the Registration Wizard.

2. Loading Client Certificate into Web Browser

The Web UI requires client certificates to authenticate users. You may still browse Registry content without authenticating, but you cannot publish, and you cannot see restricted content. Please see the User Registration Guide for how load the certificate into your web browser.

3. Loading Client Certificate into Web Browser

The Web UI requires client certificates to authenticate users. You may still browse Registry content without authenticating, but you cannot publish, and you cannot see restricted content. Please see the User Registration Guide for how load the certificate into your web browser.

4. User Authentication

Authentication is based on client certificates. These certificates are loaded into your web browser and presented to the Registry over a secure connection. Usually, https is used for this connection. Authentication happens transparently whenever you try to add, delete or modify an existing Registry object. In other words, any write request will trigger authentication based on the client certificate loaded into your web browser.

The following are some additional points:

  • After authentication is completed, you will be accessing the Registry over https. You may go back to http if you wish.
  • You may browse or querying the Registry over http. However, you may not be able to see all registry content.
  • When your session expires, you are no longer authenticated by the Registry. A subsequent write request will prompt the Web UI to reauthenticate you.