From 16f4525d43f4013010c4ac7e003d23d2a2164ddf Mon Sep 17 00:00:00 2001 From: Marek Stransky Date: Wed, 29 Nov 2023 10:01:57 +0100 Subject: [PATCH] Remove WMTPACUtils Keys from docs and add description of topt format in JWT/query --- docs/Using-Operations-Service.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/docs/Using-Operations-Service.md b/docs/Using-Operations-Service.md index b9ee493..faf524d 100644 --- a/docs/Using-Operations-Service.md +++ b/docs/Using-Operations-Service.md @@ -633,11 +633,6 @@ When authorization, the SDK will by default add `timestampSigned` to the `WMTPro /// Time-based one time password used for Proximity antifraud check public let totp: String? - - public enum Keys: String, CodingKey { - case totp = "potp" - case operationId = "oid" - } } ``` @@ -645,7 +640,10 @@ When authorization, the SDK will by default add `timestampSigned` to the `WMTPro - `parseDeeplink(url: URL) -> WMTPACData?` - uri is expected to be in format `"scheme://code=$JWT"` or `scheme://operation?oid=5b753d0d-d59a-49b7-bec4-eae258566dbb&potp=12345678}` - `parseQRCode(code: String) -> WMTPACData?` - code is to be expected in the same format as deeplink formats or as a plain JWT - mentioned JWT should be in format `{“typ”:”JWT”, “alg”:”none”}.{“oid”:”5b753d0d-d59a-49b7-bec4-eae258566dbb”, “potp”:”12345678”} ` - + + - Accepted formats: + - notice that totp key in JWT and in query shall be `potp`! + ## Error handling Every error produced by the Operations Service is of a `WMTError` type. For more information see detailed [error handling documentation](Error-Handling.md).