Skip to content

Latest commit

 

History

History
166 lines (123 loc) · 5.33 KB

README.md

File metadata and controls

166 lines (123 loc) · 5.33 KB
Raw

OpenMHealth Cert Website

Utilities to facilitate public key certificate management for NDNFit/OpenMHealth applications. Based on ndncert, and Jiewen's fork.

If set

AUTO_APPROVE = True

in settings.py, all requests would be automatically approved; otherwise, ndnop-process-requests would be needed;

Operator(s) should have /org/openmhealth as their default identity; and if set to AUTO_APPROVE, the host on which the site runs should have /org/openmhealth as its default identity; please check with

ndnsec-get-default

Name conventions for NDN certificates

User's assigned namespace is randomly generated;

User data namespace may look like

/org/openmhealth/keGKRFc81p2dkn0ebp9VgLdlJzSfJ0DKGvu1t0PGMCQZWnUcVmj2g9cAEVnH

Certificate name may look like

/org/openmhealth/KEY/keGKRFc81p2dkn0ebp9VgLdlJzSfJ0DKGvu1t0PGMCQZWnUcVmj2g9cAEVnH/ksk-1438305472389/ID-CERT/%FD%00%00%01N%E1%AF%EB%5E

Web/Mobile app interface

URL Method Parameter Action
/, /tokens/request GET None Web user facing, render token request site
Return:
200
/, /tokens/request POST email User facing, generate and store user token and namespace;
Return:
200: {“status”: 200}, success
/cert-requests/submit/ GET email, token Web user facing, render certificate submit page
Return:
200
/cert-requests/submit/ POST email, token, full_name, cert_request User facing, store user info and cert request for given token;
Return:
200: {“status”: 200}, success
403: no token/email record
500: no operator, error during ndnsec-certgen
400: user name empty, malformed cert request, cert name does not match assigned name
/cert-requests/get/ POST commandInterest Operator facing, list cert requests for certain operator;
Return:
200, list of pending cert requests
403, operator record not found
/cert/submit/ POST data, email, full_name Operator facing, store signed certificate and notify user for downloading;
Return:
200, cert approved;
400, mandatory field missing, to-add: submitted data verification failed;
500, operator not found;
403, no cert request entry;
/cert/get/ GET name, isView(optional) User facing, get certificate using certificate name;
Return:
200, NDN cert data;
404, no such certificate;

Basic operations

ndncert overview

User view

To obtain a valid NDN testbed certificate, user should follow the following steps:

  • Go to http://ndncert.named-data.net, initiate certification by submitting email address

    step 1

  • Check mailbox and click to open certification submission page

    step 2

  • Generate certification request in the specified namespace (derived from email)

    step 3

  • Submit name, other information to associate with the certificate, and public key

    step 4

  • Wait for email notification of the approval by the site’s operator

    step 5

  • Follow the instructions to install the issued certificate

    step 6

After final step the NDN Testbed certificate is installed and ready to be used.

Site operator view

Whenever users submit certification requests, operators are getting notified via email. The following highlights steps operators need to perform to issue or deny certification:

  • Wait for notification about users’ certification request(s)

    step 1

  • Log in (ssh) to the certification host

    step 2

  • Run ndnop-process-requests command and make decisions to approve/reject request

    step 3

    If ndnop-process-requests is missing, it can be downloaded using

      curl -O https://github.com/named-data/ndncert/master/ndnop-process-requests
  chmod 755 ndnop-process-requests

  # Optionally copy to a folder within $PATH. For example:
  sudo mv ndnop-process-requests /usr/local/bin/