Define logic for `Register`

[TanmoySG]

Define a operating logic for Registration through wunder Identity Provider.

• [x] Define Logic
• [x] Create Diagram - High Level (overview)
• [x] Create Diagram - Low Level (Component-wise)
• [x] Define Identity Structure (Credentials, ID, Token, what else?)
• [x] Connection/Interaction with Service Initializer
• [x] Documentation

[TanmoySG]

Defined Registration Architecture

[TanmoySG]

Identity Structure Specifications

Identifiers - email (user provided) & uID (wIP Generated)

Credentials - email & password (SHA256 Hashed)

Identity Units

Identity Units are various information bits that are stored for each user. These are provided by the user.

Email , Name , Password (hash)

Authentication Units

These are various information, like - tokens and IDs that are uses for Authentication, Authorization and Access. These are generated by the system.

uID , Admin Access Token , Core Service Configuration , Services Subscribed , Service Access Tokens

Complete Identity Structure

The following is a rough Identity Structure that will be implemented in wIP.

{
  "email" : <email> ,
  "user_uID" : <wIP Generated uID > ,
  "name" : <Name of User> ,
  "password" : <SHA-256 Hash of Password> ,
  "admin_access_token" : <wIP Provisioned Token> ,
  "services" : {
    "service_1" : {
      "service_ID" : < Same as uID> ,
      "service_name" : <Name of Service> ,
      "service_access_token" : <wIP Provisioned Token> ,
      "service_config" : <JSON describing a Initial Service Config, if any>
    },
    "service_2" : {
      "service_ID" : < Same as uID> ,
      "service_name" : <Name of Service> ,
      "service_access_token" : <wIP Provisioned Token> ,
      "service_config" : <JSON describing a Initial Service Config, if any>
    },
    ...
  }
}

Email is used as Primary Identifier for each user.

{
  "email1@test.com" : {
    "email" : <email> ,
    "user_uID" : <wIP Generated uID > ,
    "name" : <Name of User> ,
    "password" : <SHA-256 Hash of Password> ,
    "admin_access_token" : <wIP Provisioned Token> ,
    "services" : {
      "service_1" : {
        "service_ID" : < Same as uID> ,
        "service_name" : <Name of Service> ,
        "service_access_token" : <wIP Provisioned Token> ,
        "service_config" : <JSON describing a Initial Service Config, if any>
      },
      "service_2" : {
        "service_ID" : < Same as uID> ,
        "service_name" : <Name of Service> ,
        "service_access_token" : <wIP Provisioned Token> ,
        "service_config" : <JSON describing a Initial Service Config, if any>
      },
      ...
    }
  },
  "email2@test.com" : {...},
  "email3@test.com" : {...},
  ...
}

[TanmoySG]

Access Types - for reference read #8 comments or The Curious case of Login and the various Tokens.

[TanmoySG]

Updated Documentation in README.md inside the architecture directory in the dev branch.