Skip to content

Commit df732af

Browse files
author
Michael Troxler
committed
add pictures to mobile id api spec
1 parent d7cf486 commit df732af

4 files changed

Lines changed: 5 additions & 3 deletions

File tree

docs/img/async-mss-signature.png

114 KB
Loading

docs/img/mss-profile-query.png

85.7 KB
Loading

docs/img/sync-mss-receipt.png

100 KB
Loading

docs/reference-guide/mobile-id-api.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -378,6 +378,8 @@ This is an example fault response in case of an illegal MSISDN value. Each fault
378378

379379
In the asynchronous mode, the AP initiates the signature request by calling MSS_Signature method and an acknowledgment response is sent back immediately by the MID to AP. The AP client then starts poll-ing using MSS_StatusQuery service to receive the response as depicted below.
380380

381+
![async-mss-signature](/img/async-mss-signature.png)
382+
381383

382384
1. End-User uses an application that sends an authentication request.
383385
2. AP receives the request and sends an asynchronous MSS_SignatureReq request message to MSSP.
@@ -1592,7 +1594,7 @@ Only synchronous Signature Receipts are supported. There is no support for async
15921594
### Synchronous MSS Receipt
15931595
In the synchronous mode, the AP initiates the receipt request by calling MSS_ReceiptReq, which is then blocked until the signature has been acknowledged, cancelled or the signing times out occurs. The picture depicted below, shows the successful case.
15941596

1595-
**INSERT PICTURE**
1597+
![sync-mss-receipt](/img/sync-mss-receipt.png)
15961598

15971599
1. For each successful MSS_SignatureResp the AP can request an MSS_ReceiptReq by passing the same MSSP_TransID and same MSISDN from the MSS_SignatureResp and defining message to be displayed to the End-User.
15981600
2. MID backend checks the credentials.
@@ -1807,7 +1809,7 @@ An AP may use this operation to check the Mobile ID status and signature capabil
18071809

18081810
The AP can use a Profile Query request as depicted below.
18091811

1810-
**INSERT PICTURE**
1812+
![mss-profile-query](/img/mss-profile-query.png)
18111813

18121814
1. Before to send a signature request for authentication, the AP validates the status and signa-ture profile capabilities of a Mobile ID user by sending an MSS_ProfileReq request to Mobile ID
18131815
2. MSSP checks the user status and signature capabilities
@@ -1817,7 +1819,7 @@ The AP can use a Profile Query request as depicted below.
18171819

18181820
### MSS Profile Query Request
18191821

1820-
The lines highlighted in pink are optional Profile Query Extension parameters (see section [MSS Profile Query Request Extensions](/reference-guide/moblie-id-api#mss-profile-query-request-extensions)).
1822+
The lines highlighted in pink are optional Profile Query Extension parameters (see section [MSS Profile Query Request Extensions](/reference-guide/mobile-id-api#mss-profile-query-request-extensions)).
18211823

18221824
::: code-group
18231825

0 commit comments

Comments
 (0)