MobilSITHS

HTTP wrapper to simplify accessing SITHS.

Introduction

Communicate with SITHS backend. Most common usage is in conjunction with an API exposed to clients wanting to leverage SITHS functionality, auth & sign.

Data is sent to SITHS with out any transformation.

For information on how to format the request data consult SITHS API documentation.

Configuration

Valve name: MobilSITHS

Properties

Name	Description	Default value	Mandatory	Expanded
http_destination	The script engine to use.	"default"
mode	Allowed value is one of: AUTH,COLLECT,CANCEL or SIGN	N/A
backend_endpoint	SITHS backend endpoint.	N/A

Example

{
    "name": "MobilSITHS",
    "config": {
        "http_destination": "siths_http_client",
        "mode":"AUTH",
        "backend_endpoint":"https://secure-authservice.qa.siths.se"
    }
}

Request data

Data sent to SITHS is the entire pipe request. This must conform to any SITHS requirements.

Response

Response data from SITHS backend is sent back to calling client without any transformation with one exception:

On mode "COLLECT" and response is "complete" the JSON response is enriched with "subject" in "completionData" -> "credentialInformation". This will only occure in response certificate contains RDN with identifier-id "2.5.4.5"