[英]Automatic SMS Verification with Authy
I developped a mobile app using our backend to register and verify users using Authy. 我使用后端开发了一个移动应用程序,以使用Authy注册和验证用户。 This is done by the backend in 3 steps: 后端通过3个步骤完成此操作:
1/ The app requests the backend to register the user. 1 /应用程序请求后端注册用户。 The backend calls https://api.authy.com/protected/json/users/new (email, cellphone, countrycode). 后端调用https://api.authy.com/protected/json/users/new (电子邮件,手机,国家/地区代码)。 It provides back the userId later used. 它提供后面使用的userId。
2/ The app requests the backend to send a sms code the user. 2 /应用程序请求后端向用户发送短信代码。 The backend calls https://api.authy.com/protected/json/sms/ {1}?locale={2}{3}" (userId, language, force) 后端调用https://api.authy.com/protected/json/sms/ {1}?locale = {2} {3}“(userId,语言,强制)
3/ The user now receives the SMS. 3 /用户现在收到SMS。 He fills it in the mobile app, which eventually is sent to the backend for verification. 他将其填充到移动应用程序中,最终将其发送到后端进行验证。 The backend calls https://api.authy.com/protected/json/verify/ {1}/{2}{3}" (token, userId, force) 后端调用https://api.authy.com/protected/json/verify/ {1} / {2} {3}“(令牌,userId,强制)
I wanted to use Automatic SMS Verification with the SMS Retriever API in my mobile app ( https://developers.google.com/identity/sms-retriever/overview ) to avoid the hassle for the user to enter his verification code. 我想在我的移动应用程序( https://developers.google.com/identity/sms-retriever/overview )中将自动SMS验证与SMS检索器API结合使用,以避免用户输入验证码的麻烦。 It requres to set up a hash in the verification code, but unfortunately I don't seem to have any control on what Authy generates. 它要求在验证代码中设置哈希,但不幸的是,我似乎对Authy生成的内容没有任何控制权。
Am I missing something here to get it work? 我是否在这里缺少一些东西以使其正常工作?
Rgds RGDS
R. R.
No, you just can't affect the text in Authy's SMS. 不,您只是不能影响Authy的SMS中的文本。 So, for now, it looks like we can't support retriever API. 因此,目前看来,我们不支持检索器API。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.