Only this pageAll pages
Powered by GitBook
1 of 6

1.0 Mobile Server

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

MobileServerDatabaseJdbc

The database used by MobileID

Introduction

A database module for MobileID

Configuration

Module name: MobileServerDatabaseJdbc

Configuration

This is the configuration.

Name
Description
Default
Mandatory

db_driver

Should be "com.microsoft.sqlserver.jdbc.SQLServerDriver"

N/A

jdbc

The description of the jdbc source. url, username, password

N/A

{
  "name": "MobileServerDatabaseJdbc",
  "config": 
  {
    "db_driver": "com.microsoft.sqlserver.jdbc.SQLServerDriver",
    "jdbc": 
    {
      "url": "jdbc:sqlserver://172.16.238.15:1433;database=databasename;encrypt=false",
      "username": "sa",
      "password": "password"
    }
  }
}

MobileServerServerModule

The server api of MobileID

Introduction

Server side http api for MobileID. The api should not be accessible from Internet.

Configuration

Module name: MobileServerServerModule

Configuration

This is the configuration. All http configuration parameters is also valid.

Name
Description
Default
Mandatory

issuer

Modules within the same namespace belong together.

N/A

issuer_id

A GUID identifier for this issuer. Can be generated here:

N/A

client_api_url

External url used by the mobile clients

N/A

url_scheme

Scheme used for QR-codes etc. Must be "fortifiedid"

fortifiedid

{
  "name": "MobileServerServerModule",
  "config": 
  {
    "http_context": "/mos",
    "issuer": "Fortified ID",
    "issuer_id": "<should be a guid>",
    "client_api_url": "http://192.168.86.27:7002/mosclient",
    "http_port": 7001
  }
}
https://www.guidgenerator.com/

MobileServerEnrollment

The enrollment module of MobileID

Introduction

Server enrollmept api for MobileID.

Configuration

Module name: MobileServerEnrollment

Configuration

This is the configuration.

Name
Description
Default
Mandatory

flow_layout

The layout used. Possible values are STANDARD or MINIMAL

STANDARD

server_api_url

Address to communicate with the server module

N/A

validity

The validity of the generated certificates. Use one of the following formats: P365D - for 365 days PT8H - for 8 hours Overrides the setting in the CA-module

P730D (Two years)

{
  "name": "MobileServerEnrollment",
  "config": {
    "http_context": "/enrollment",
    "context_path": "/mobileid",
    "validity" : "P365D",
    "server_api_url": "http://192.168.86.27:7001/mos",
    "flow_layout": "STANDARD",
    "http_auth_redirect_url": "/enrollment/authn/myauth",
    "http_port": 8080
  }
}

Form-format

This document describes the format of the form used in Tasks.

Concept

The form is build up by stacking elements from top to bottom using a json format.

Requirements

The form must consist of:

  • At least one element

  • At least one button_confirm

  • Only one background element

  • Only one title element

  • All elements must have unique id's

Entities

<color>

is specified using the format #aarrggbb (for instance #ffff0000 or #774499cc).

<image>

is represented by a base64-representation of a jpeg or png image.

Types of elements

title

The title element is presented as a text in the titlebar

Example

{"id":"1","type":"title","value":"Login to VPN"}

background

The background fills the entire form. It's value can either be a <color> or an <image>

Example:

{"id":"2","type":"background","value":"#ffff0000"} {"id":"2","type":"background","value":""}

image

The image value is an <image> stretched to full width and scaled in height keeping the aspect ratio. A preferable pixel-width of the image is 640.

Attributes:

background_color - <color>

Example:

{"id":"3","type":"image","value":""} {"id":"3","type":"image","value":"", "background_color":"#ff005500"}

label

Label displays a text which are wrapped if the width exceeds the task-width

Attributes:

text_color: <color> text_size: "thin", "extra_small", "small", "medium", "large", "extra_large" text_alignment: "left", "center", "right" text_bold: "true", "false" background_color: <color>

Example:

{"id":"3","type":"label","value":"Hello World!"} {"id":"3","type":"label","value":"Hello World!", "text_color":"#ff0000ff", "text_size":"small", "text_alignment":"right", "text_bold":"true"}

button_confirm & button_reject

Note: Two or more consecutive buttons are displayed side-by-side. If this effect is not desired, separate them with small padding.

Attributes:

text_color: <color> button_color: <color> background_color: <color>

Example:

{"id":"4","type":"button_confirm","value":"Login"} {"id":"4","type":"button_confirm","value":"Login", "text_color":"#ff000000", "button_color":"#ffffaaaa"}

padding

Note: Dynamic padding "eats up" the remaining vertical space of the form. Multiple dynamic padding shares this space equal. All other paddings are fixed sizes.

Possible values: "dynamic", "thin", "extra_small", "small", "medium", "large", "extra_large"

Attributes:

background_color: <color>

Example: {"id":"5","type":"padding","value":"dynamic"} {"id":"5","type":"padding","value":"large", "background_color":"#ffff0000"}

Examples

Example 1

{
   "elements":
   [
      {"id":"1","type":"button_confirm","value":"Confirm"}
   ]
}

Example 2

{
   "elements":
   [
      {"id":"1","type":"title","value":"Login"},
      {"id":"2","type":"background","value":"#ffccccff"},
      {"id":"3","type":"padding","value":"dynamic"},
      {"id":"4","type":"button_confirm","value":"Confirm"},
      {"id":"5","type":"button_reject","value":"Reject"},
      {"id":"6","type":"padding","value":"dynamic"}
   ]
}

Example 3

{
   "elements":
   [
      {"id":"1","type":"title","value":"Confirm login"},
      {"id":"2","type":"background","value":"#ff444499"},
      {"id":"3","type":"padding","value":"dynamic"},
      {"id":"4","type":"label","value":"Welcome!", "text_color":"#ffffffff", "text_size":"large", "text_bold":"true"},
      {"id":"5","type":"label","value":"Confirm your login", "text_size":"small"},
      {"id":"6","type":"padding","value":"extra_large"},
      {"id":"7","type":"button_confirm","value":"Confirm"},
      {"id":"8","type":"button_reject","value":"Reject"},
      {"id":"9","type":"padding","value":"dynamic"}
   ]
}

MobileServerInternalCA

The CA used by MobileID

Introduction

A module that generates certificates

Configuration

Module name: MobileServerInternalCA

Configuration

This is the configuration.

Name
Description
Default
Mandatory

keystore

The keystore containing the certificate and private key. Can be specified as data or as a file.

N/A

validity

The validity of the generated certificates. Use one of the following formats: P365D - for 365 days PT8H - for 8 hours

N/A

{
  "name": "MobileServerInternalCA",
  "config": 
  {
    "key_store": 
    {
      "data": "MIIKngIBAzCCC1M...gInEA",
      "private_key_password": "password",
      "password": "password"
    },
    "validity": "P365D"
  }
}

MobileServerClientModule

The client api of MobileID

Introduction

Client side http api for MobileID. The api must be accessible from Internet.

Configuration

Module name: MobileServerClientModule

Configuration

This is the configuration. All http configuration parameters is also valid.

{
  "name": "MobileServerClientModule",
  "config": 
  {
    "http_context": "/mosclient",
    "http_port": 7002
  }
}

Just one element, a confirm button.