Metaforik Technical Details¶

• Metaforik Technical Details
• Structure of the Metaforik Service
• How the Service is used
• Item Management Characteristics
• User Management Characteristics
• Interaction with Metaforik System
• Primary Requests
• Ancillary Requests
• Request Mechanism: Via URI
• Comments

Aims of this section:

Per Metaforik Service.

Structure of the Metaforik Service¶

Questions: Who uses each sub-domain?

How the Service is used¶

One Service = One Metaforik Server (or mirrored instances of the server)

• VastPark uses one server for the internet as a whole.
• Private instances of the server are available for use for our enterprise clients

• Domains [One Domain Per Metaforik Service]
• Sub-Domains [Multiple sub-Domains in a Metaforik Service]
• Items (everything is an item in Metaforik) Many Items per service, multiple types of items
  Each item is associated with one Subdomain and one publisher.
  • Identity Management: (one type of items)
    • Groups are one type of item. Each group has one or many users.

Item Management Characteristics¶

• Permissions for each Item
  On the basis of Domain (subDomian), Persona (User) as well as Group (Multiple Users) scopes.
  • Whitelist (allowed Domain/User/Group)
  • Blacklist (dis-allowed Domain/User/Group)

User Management Characteristics¶

Personas and Users

how to get one user across different sub-domains.

Interaction with Metaforik System¶

Primary Requests¶

Get – Get an item from the service
Put – Put an item to the service
Find – Find an item in the service
Remove – Remove an item from the service

Ancillary Requests¶

VerifyUser – Verifies a sessionkey/alias combination are valid
Login
Logout

Request Mechanism: Via URI¶

vp://subdomain.domain/get/alias1

Example: Get User Profile

Request URI: vp://subdomain.domain/get/alias1

How the system checks: