Application Providers

Application providers (APs) can use the demo environment for software testing.

General

Uptime of the demo environment is not guaranteed. It will be mostly up but there are occasional maintenance breaks. To check the AE service state you can visit the AE service state page.

MSSAPI

Demo acquiring entity (AE) implements the ETSI TS 102 204 SOAP interface.

Solution_Overview_Demo_AP_MSS_Client_model

Demo AP ID is “http://demo_ap” and password is “demo“. You can use demo-keystore and demo-truststore with SSL connection. Demo AE authenticates AP with a password or certificate.

Use following URLs to make ETSI 204 requests with SSL connection:

  • Signature – https://mssp.demo.methics.fi:9011/soap/services/MSS_SignaturePort
  • Status – https://mssp.demo.methics.fi:9011/soap/services/MSS_StatusQueryPort
  • Receipt – https://mssp.demo.methics.fi:9011/soap/services/MSS_ReceiptPort

Use following URLs to make ETSI 204 requests with plain connection:

  • Signature – http://mssp.demo.methics.fi:9010/soap/services/MSS_SignaturePort
  • Status – http://mssp.demo.methics.fi:9010/soap/services/MSS_StatusQueryPort
  • Receipt – http://mssp.demo.methics.fi:9010/soap/services/MSS_ReceiptPort

The following MSS Formats are supported:

  • http://uri.etsi.org/TS102204/v1.1.2#CMS-Signature
  • http://uri.etsi.org/TS102204/v1.1.2#PKCS7
  • http://uri.etsi.org/TS102204/v1.1.2#PKCS#10
  • http://www.methics.fi/KiuruMSSP/v3.2.0#PKCS1

You can use, for example, the Laverca as an MSS Client.

REST API

Demo REST API is a RESTful alternative to the SOAP interface.

Solution_Overview_Demo_AP_RESTful_MSS_Client_model

Demo is behind basic authentication. Use username “rest” and password “rest“. REST API AP ID is “http://test1_ap” and password is “password“.

Instructions for REST API can be found in the docs in the help page. Demo REST API uses following service URLs:

Plain – http://mssp.demo.methics.fi/rest/service
Secure – https://mssp.demo.methics.fi/rest/service

You can try REST API requests with the JavaScript UI. JS UI uses libraries found in scripts.

Mobile user simulation

Mobile user MSISDN “+358 4700 1001” is simulated using the WPKI Simulator and will instantly respond to all requests. This MSISDN does not use the noSpam code additional service.

You can also use an interactive phone which acquires a separate MSISDN.

Certain situations which would be possible with a real mobile user are reproducible in the demo environment.

Use one of the delay commands in “DataToBeSigned” element of the signature request. Simulator will wait specified amount of milliseconds before responding. Delay commands

  • DELAY_500
  • DELAY_1000
  • DELAY_2000
  • DELAY_5000
  • DELAY_10000
  • DELAY_30000
  • DELAY_60000

Use one of the error commands in “DataToBeSigned” element of the signature request. AMS Simulator will produce the simulated error. Error commands

  • ALAUDA_ERROR_Concatenation_Error
  • ALAUDA_ERROR_Decryption_Error
  • ALAUDA_ERROR_Encryption_Error
  • ALAUDA_ERROR_Internal_Error
  • ALAUDA_ERROR_Key_Group_Error
  • ALAUDA_ERROR_Key_Index_Error
  • ALAUDA_ERROR_ME_not_supported_error
  • ALAUDA_ERROR_Missing_Configuration_or_content
  • ALAUDA_ERROR_Missing_Display_Text_TLVs
  • ALAUDA_ERROR_Missing_Parameter
  • ALAUDA_ERROR_Not_Supported_Data_To_Be_Signed
  • ALAUDA_ERROR_No_Active_Keys
  • ALAUDA_ERROR_PIN_Blocked
  • ALAUDA_ERROR_Signing_Error
  • ALAUDA_ERROR_Timeout_Error
  • ALAUDA_ERROR_User_Cancel
  • ALAUDA_ERROR_Wrong_encryption_counter
  • ALAUDA_ERROR_Wrong_Verification_Code