You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/reference-guide/mobile-id-api.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -378,6 +378,8 @@ This is an example fault response in case of an illegal MSISDN value. Each fault
378
378
379
379
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.
1. End-User uses an application that sends an authentication request.
383
385
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
1592
1594
### Synchronous MSS Receipt
1593
1595
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.
1594
1596
1595
-
**INSERT PICTURE**
1597
+

1596
1598
1597
1599
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.
1598
1600
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
1807
1809
1808
1810
The AP can use a Profile Query request as depicted below.
1809
1811
1810
-
**INSERT PICTURE**
1812
+

1811
1813
1812
1814
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
1813
1815
2. MSSP checks the user status and signature capabilities
@@ -1817,7 +1819,7 @@ The AP can use a Profile Query request as depicted below.
1817
1819
1818
1820
### MSS Profile Query Request
1819
1821
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)).
0 commit comments