I am using cypress and mailhog to test email validation step of the sign up process on our staging site. Currently the test is failing with a 401 status code - the mailhog inbox requires a username and password.
How can I pass a username and password into the API request?
I have followed installation, setup and usage steps in the cypress-mailhog docs.
Related
We have authenticated kong with RBAC credentials. Before this, we are able to hit localhost:8001/default/apis?size=100. But after applying RBAC authentication, we are getting the below error
{
"message": "Invalid RBAC credentials. Token or User credentials required"
}
Please help with the steps to run this on browser or as curl request.
If you followed the installation instruction, Kong advised seeding Super Admin token.
This token can be used with appropriate header when calling Admin API.
For example using default header with token value 'password':
curl http://kong-ip:8001/ --header 'Kong-Admin-Token: password'
If you miss the step of seeding super admin. following this instruction to seed admin token and use it with header from prior reference.
i'm migrating our current custom SMTP mail server for Firebase Authentication mails to Amazon SES. I generated new SMTP credentials and updated the Firebase SMTP settings:
But when i try to send a password reset mail, i continuously receive this error in the sender's inbox: 554 Transaction failed: Missing final '#domain'.
The same SES SMTP credentials work fine (= emails being sent), when i use them (base64 encoded) in a local CLI script (https://docs.aws.amazon.com/ses/latest/DeveloperGuide/send-email-smtp-client-command-line.html) or on https://www.smtper.net/.
Additional information:
inspired by the error message, i tried to add my maildomain to the SMTP user's name (ABCDEFGHIJKLMNO#mydomain.net) but received the error 535 Authentication Credentials Invalid
i did not use the account's credentials (as mentioned in most topics), but the SMTP user's credentials
as mentioned in other related topics, i also tried to URL encode the password with no avail (it contains a /). Same for base64 encoding the password
the custom domain and the sender's address are verified in SES
i have configured SPF and DKIM for the custom mail domain (also verified)
If i missed any further information, please let me know, thanks in advance.
I'm developing a firebase web project where user can sign up and login via email / password.
Right now, when I send a verification email (firebase.auth().currentUser.sendEmailVerification()).
When I receive the email (few seconds later) and follow the link, I just get this error:
However, my email is still not verified - and there are no further error messages. How can I complete the email verification?
Retrying the procedure gives me a different link each time, but with the same result.
I'm a user getting an OAUTH fail when trying to login to FounderDating. I'm getting a confirmed email address issue when I've confirmed my email is valid with LinkedIn. This has happened on other sites as well. Any solutions from LinkedIn?
I've successfully installed and tested the OAuth 2 workflow with Symfony 2 and FOSOAuthServerBundle.
I can request a code, and get a pair of access/refresh token successfully from a "login with" button on a third party test page i've set up and retrieve a user from my API through a custom API call. Pretty cool here.
However, each time I test the flow from the beginning, my oAuth server keeps on redirecting the user on the authorization page. Here are my questions.
Once a user has authorized and app, shouldn't the authorization part of the process be skipped with OAuth 2.0 ?
Is that fixed on the server side or should i change the way i request the credentials on client site ?
And finally... could i debug and fix this ?
If anyone struggles again, the solution is here :
https://github.com/FriendsOfSymfony/FOSOAuthServerBundle/blob/master/Resources/doc/the_oauth_event_class.md
This feature is not default in FOSOAuthServer bundle. You have to create and EventListener and check client or user status, save the user's choice, and [quote:even bypass the authorization process].