Pinpoint SMS OTP: Amount of retries

0

Hi,

I use SMS OTP in my application which works fine. But if a customer gets a SMS and have to input the code within our application I struggle how to detect the amount of retries. (Of course I can do this on client side)

So if I set AllowedAttempts = 3 and send 10 times the same wrong code I do not know how many attempts are left nor that the maximal number of attempts are exceeded. This feels like a bug for me.

{
   "ResponseMetadata":{
      "RequestId":"xxxxx",
      "HTTPStatusCode":200,
      "HTTPHeaders":{
         "content-type":"application/json",
         "content-length":"15",
         "connection":"keep-alive",
         "date":"Sat, 23 Jul 2022 15:19:28 GMT",
         "x-amzn-requestid":"xxxx",
         "access-control-allow-origin":"*",
         "x-amz-apigw-id":"VuesDF7pliAFecQ=",
         "cache-control":"no-store",
         "x-amzn-trace-id":"xxxx",
         "x-cache":"Miss from cloudfront",
         "via":"xxxxx.cloudfront.net (CloudFront)",
         "x-amz-cf-pop":"FRA56-P2",
         "x-amz-cf-id":"xxxxx"
      },
      "RetryAttempts":0
   },
   "VerificationResponse":{
      "Valid":false
   }
}

Why is "RetryAttempts":0 not changing? It is always 0? The Valid field is changing to true if I send within 3 attempts the correct code otherwise it stays allways false.

Any idea what is going on here?

已提問 2 年前檢視次數 68 次
沒有答案

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南