In this link, https://firebase.google.com/docs/auth/ios/phone-auth send phone number verification code is provided.But is there any solution to resend OTP in the same number in iOS.
I have also wanted this, but on testing and checking example firebase app, resending was same as generating it first time i.e PhoneAuthProvider.provider().verifyPhoneNumber(Swift) unlike android where in we send resend token.
Related
I have a service that listens for certain updates and then uses a Discord Bot to post a message on a channel. A random example: every time a team scores a goal, post a message in a channel. I got an email from Discord to reset my bot token because there were too many logins.
As you know, in order to use the Bot you use the client.login("XXX") method. So every time there is an update my service initializes the bot and then sends a message. My assumption is that it has to do with me calling client.login("XXX") for every update. Since my service runs serverless, I can not keep the service up.
Is there a way to make the bot post a message without having to use client.login("XXX")? Or can anyone suggest any strategy to make this logic work?
That is not possible as a bot cannot do any actions without being logged in, it sounds like channel webhooks would fit your needs better.
You simply generate a webhook link in a channel which you can then post messages to through a post request.
You can read more about webhooks here
And you can read more about the required paramters and how to format a POST request to the webhook here
In our application, when a user signs up they get a one time verification email with a link that they click to confirm the email (VERIFY YOUR EMAIL BY CLICKING THIS LINK). This then usually sends a confirmation email, but instead seems to also send the user a phone SMS message with a phone verification code when the link is clicked (Your verification code is: XXXXX). For context this text is supposed to be sent (and is also sent) when the user signs in. It seems Cognito is getting its steps mixed up, has anyone ran into this before? Any help would be amazing. Thank you!
PS. We are using Node.js for the lambda functions. We use a pre signup lambda, a post confirmation lambda and a post auth lambda that logs information.
This problem first appeared when needing to re-register our toll free number when texts started failing to go through during our registration process. We then waited for the number to get through the vetting process and afterwards the double text issue was still occurring.
The next thing we tried doing was removing all code from the situation (lambda triggers on the user pool) and run the sign in/sign up process. We thought that since in the post confirmation lambda there was code sending the SES email for email verification something may be wrong there. When removing all the triggers and hitting the default email link verification it still sent an SMS.
Lastly, we then tried making a whole separate user pool with the same configuration and no users/ with imported users. Cognito still sent a text (Your verification code is: XXXXX) to the user's phone after they hit the VERIFY YOUR EMAIL HERE link.
I implemented DocuSign webhooks using ngrok, but the notification takes about 20-25 seconds to hit the application API. Can anyone please verify is this the normal time that it takes to send a notification?
Yes that is normal.
Especially in the Developer Environment (demo, formally known as the "sandbox").
In production this time is shorter and it's faster to get the notification into your webhook.
Conversation Flow : android device/web simulator - google assistant - api.ai - webhook - [websocket/FCM push] - android device
From end of last week, access token is not delivered to our webhook server even if account linking was successful and it is displayed on web simulator debugging window. When we logged on webhook server, the account token value from api.ai was NULL. After this happened, next account linking is not processed even if I reset (turn it off and on again) api.ai agent.
I tried to make new actions project and migrate api.ai agent to new one, but it was the same. I make sure the same test has been successful before last week.
If anyone has gone through the similar issue, I hope your help.
I was also very confused because I was expecting the accessToken to be in the same JSON format as shown in the simulator.
if still not working please send the body of the request you receive not what the simulator show you.
but it's under originalRequest.data.user.accessToken.
if you are using NodeJS you don't need to parse anything you will just need to call :
getUser().accessToken
from ApiAiApp object in the actions-on-google node library.
I basically am trying to allow users to post to their blog using a text message. I have a phone number stored for each user, and since twilio sends that information in the post request they hand to my page, I can do a reverse lookup to see which blog to post it to. The question now arises, how can I be sure that the user sent the text? Can't anyone just send post information with someone else's phone number?
I have a couple thoughts about this:
1. Twilio sends your account number in the post, which I suppose isnt known to malicious users.
2. I could respond with an SMS containing a randomly generated code, and have the user send that back. This would effectively triple the SMSs needes do I would prefer the first.
Is number one "safe enough"? Or should I bite the bullet and make a response system as in number two?
You can verify that requests are coming from Twilio. We attach an X-Twilio-Signature header to each request which is signed with your Auth Token (which should be known only by you). Each of the Twilio helper libraries has a function to help determine if the request was made by Twilio or not.
Please see our documentation on validating requests: http://www.twilio.com/docs/security#validating-requests
or our helper library functions for validating Twilio requests: http://readthedocs.org/docs/twilio-php/en/latest/usage/validation.html#validate-incoming-requests, for example.