I tried to signup with my email using aws cognito. I received the email verification link and when i clicked on it says 'Invalid link provided, please request a link again'. But when i tried to login it was successful. Why is it happening.
This could be caused by your Email provider visiting links before presenting the email to you. For example Outlook has something called Safe Links. This will cause the verification link to be consumed before you have a chance to click it.
I had the same issue and after about a day of debugging I reached out to AWS Enterprise Support. Outlook Safe Links is something they mentioned within a few minutes of chatting. If you are a part of a larger organization it is probably unfeasible to have it disabled. You can try signing up with a different Email Provider such as Gmail and see if the links are untouched.
I offer no solution to the problem, just a possible explanation.
Related
I cannot sign into AWS account. The AWS management console accepts password but then throws 400 error before getting to MFA. Link to Support takes me to login again, haha. I cleared cache and cookies for all of time. I tried different browsers and devices.
I had the same problem and the same unsuccessful attempts to resolve. It now appears to be fixed at least for me. Hopefully for you all as well.
According to AWS support, they said that I have two AWS accounts. That means my Amazon.com account also counts as an AWS account I guess. Both have the same email address, e.g. myemail#gmail.com. Therefore, the below StackOverflow link fixed my issue.
I just had to modify my Amazon.com email to include +amazon so if it was myemail#gmail.com, then I needed to change it to myemail+amazon#gmail.com. Do this by logging into Amazon.com, then navigate to Your Account > Login & security
Don't worry, you don't actually need to create an email for myemail+amazon#gmail.com
Seems like Amazon.com removes the +amazon and continues to treat it as myemail#gmail.com as far as I've noticed so far. You are still even allowed to log into Amazon.com with myemail#gmail.com without adding the +amazon
After doing this, I was able to log into AWS account as usual. =)
Source: https://stackoverflow.com/a/57104601
I contacted AWS support (like the OP, I had to convince them that "log in to your account to get support when you can't log in to your account" was unreasonable) and they fixed the problem for me but unfortunately provided no details on what caused it. In case anyone missed it in the comment on the question, support when you can't log in is at https://support.aws.amazon.com/#/contacts/aws-account-support .
When I'm validating the account by clicking the link given in email during account verification process(sign up process), I'm getting below error. Can you please suggest what is causing this error?
enter image description here
In the self-registration config section, there is a configuration for callback validation. It is provided as a regex. Make sure you have configured it properly.
Google processed my Business Messages partner registration and my project has already get Partner ID and Partner Project.
But when I try to activate API in library from this url: https://console.developers.google.com/apis/library/businessmessages.googleapis.com
I've got the error:
An error occurred while loading
/apis/library/businessmessages.googleapis.com?project=mybusiness-152610&folder=&organizationId=.
Try again.
ID request : 3154477086545573582
I don't know what's wrong, if someone has an idea how to avoid it please, I already follow all steps in their documentation
Thank you so much
I just read the mail from Google BM-support again and found this.
"We have granted your email address access to the Business Messages API, Business Communications API". I think if your cloud account isn't same as the email you were granted, then you can't search Business Message API.
And it said ...
"Please reply to this email, or send a new email to bm-support#google.com, to request access for additional email addresses."
Maybe you can try to write a mail to bm-support#google.com ..
I'll do it.
We’ve created successful a bot and also can test with page token generated from facebook developer portal (the token must contain page_messagaging permission to be able to send reply message).
But when we submit to facebook to review, it seems they use real account to test and the token doesn’t contain page_messaging permission. (log from our server says: {“error”:{“message”:”Unsupported post request. Object with ID ‘me’ does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api”,”type”:”GraphMethodException”,”code”:100,”fbtrace_id”:”DPdtxdcTKaf”}})
The submission has been rejected 3 times now.
And have no solution now.
Anyone experience in this? Could you please help us resolve?
Really appreciate!
I'm writing an Amazon Skill that I want hooked up with a google account via oauth2. In my edit skill page, I configured it with my client id, an authorization url and token url from the oauth playground, and made it an authoritative grant with my secret and authentication scheme of "http basic", which is recommended.
I tested my client id/secret in the oauth playground and it works as I expect it to, but when I go to sign in on the Alexa App, I get a "missing redirect_uri" error. Looking at the link in the popup, it looks like the following:
https://accounts.google.com/o/oauth2/auth?client_id=custom_client_id&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email
Why is it missing the redirect_uri parameter? I can't change it on the skills page, it's set, and I added it to my valid redirect_uri lists on the google console. Anyone else seen this issue before?
An easier version of what jking31cs is saying is to include ?redirect_uri= ...
In your base URL. So if you provide them Oath.com/auth as your authorization URL, instead try Oath.com/auth?redirect_uri=
The redirect URI is constant, so this is a good fix until amazon bothers fixing this. It's only an issue on custom skills.
They've fixed the issue with an update to the Alexa App :D