I'm trying to set up an Email Watcher node to watch a gmail account for incoming emails, and have specified the properties. However, that step of the workflow fails with:
imap.gmail.com is not ready for : AUTHORIZATION.
Any idea what the cause of this would be?
You can use the IMAP Watcher instead of the Email Watcher node.
Related
I have a case where we use custom Authorization in Kubernetes via a webhook. Once authorized is there any way the user id could propagated on to the metadata or labels or env of a resource in Kubernetes.
Eg - When a user creates a pod, the userid should be available on the request object.
The only place where the user data is available is in the events that is available via audit logs.
You could use a mutating webhook to inject it. The webhook admission request struct has the user identity data and you can patch the incoming object in the admission response. There is nothing off the shelf for that though, you would have to build it yourself.
My goal is to somehow send the email and click the link to reset the password, access that link and write a new password. Don't really know if this is possible or could only be mocked.
I would also like to catch the content of the email and check it. Is there a way within TestCafe to do this?
You can use TestCafe to fill out and submit the password recovery form that will initiate a request to your backend. After that, you can use either of the following solutions:
Intercept this request to the backend using TestCafe features for Intercepting HTTP Requests. Then, make sure that the "an email with a retrieval link was sent" message was shown, navigate to the known in advance retrieval link and log in with a new password.
Make this request to the backend actually initiate sending an email. Then, in your test, connect to an email service (using some of the Node.js email clients), receive the email, and navigate TestCafe to the link.
The first approach seems to be more robust because it doesn't rely on any third-party services.
I'm building an application with AWS Cognito and AWS AppSync.
My Problem:
I want to an User, after signUp, for some reason (not important) he did not receive the Verification E-mail (which is a Link, not a Code).
The user goes back to the application and asks for another Verification E-mail.
Tried:
I tried the following solutions,
-> Using resendConfirmationCode function of AWS-SDK.
-> Using Auth Amplify API with the function resendSignUp[
-> Using the following npm package (https://www.npmjs.com/package/amazon-cognito-identity-js) Use Case #3
I Always end up on this message: "Cannot reset password for the user as there is no registered/verified email or phone_number"
I want that the function resends the verification Link to an User, so he does not have a E-mail verified yet.
What do I expect?
If the user does not receive an E-mail with the verification Link, he can use a function to call again for this e-mail.
As I'm working with Links, I would rather prefer a Link for this, but if is not possible, a Code will be fine, and I change it on Cognito Lambda-Triggers.
Hope you guys be able to help me :)
I have followed the guide for github pipeline triggers via webhooks and while I can verify that the webhook was sent successfully with the exact filepath artifact, my pipeline is not triggered.
I have verified the artifact expected is sent and the response is 200 from github with body:
{"eventId":"5a05b1b0-ac9f-4222-bdeb-caa1a7f4b216","eventProcessed":true}
I have checked the echo log and there doesn't seem to be anything but startup information. It must not be logging webhooks and responses, or else I figured I would see the ^^eventId I received on the github side.
Here is a gist with this information including the payload.
Below is an image of the pipeline config - at this time I'm just trying to trigger it and get a slack notification, but nothing is triggered:
What am I missing here? How can I debug further?
I found the error thanks to Pere on the spinnaker slack channel.
I have the spinnaker trigger watching master (which is what I want for production), and I was commit/pushing test files to develop. So while the webhook is configured to push for any case, it is filtering it on the spinnaker side. Changing the trigger to watch develop worked.
As a side note, neither successful nor unsuccessful triggers showed in the echo log.
When I execute the following code,
Cloud.Users.requestResetPassword({
email: myUsersEmailAddress
}, function (e) {
if (e.success) {
Ti.API.info('Success: Reset Request Sent ' + JSON.stringify(e));
} else {
Ti.API.error('Error:\n' + ((e.error && e.message) || JSON.stringify(e)));
}
});
I should receive an email to reset my password, as seen in the documentation:
GET users/request_reset_password.json Sends an email to a user
containing a link to recover a lost password. You can use the default
email template provided by ACS, or specify a custom email template
that you have created. When using a custom email template, the email
must contain a properly formatted URL, as explained in the template
method parameter documentation below.
When the alert pops up, I can see that there was a match and that an email should have been sent.
However, I do not receive an email, nor do I see anything in the logs of my email backend (which does receive an email when I adapt my email configuration on the appc backend, thus my email is correctly configured)
I don't have any email templates configured, but according to the documentation it should use appc's default reset password email.
Does anyone has an idea about what I am doing wrong, or does this indicate an issue with appc's documentation or backend?
UPDATE: I have another function which sends email using a self-defined email template. When I invoke this function, i receive the following event(between the {}):
[INFO] : Deactivation email sent. {"success":true,"error":false,"meta":{"status":"ok","code":200,"method_name":"emailFromTemplate"}}
However, nothing is seen on our smtp backend. The only things we do see (and which we receive in our mailbox) are the emails which are sent when you adapt your email configuration settings in Appcelerator's backend, eg.
Subject: Appcelerator Cloud Services SMTP Test
Appcelerator Logo Hi Peter,
Your SMTP settings have been updated successfully!
Onward,
The Appcelerator Platform Team
Thanks,
David
It turned out to be a configuration issue, which could only be discovered by doing some curl calls against the api. So a good advice, test your config with curl too, and don't rely on the emails which are sent after you made a configuration change!