SMTPSenderRefused at /password_reset/
(530, b'5.5.1 Authentication Required. Learn more at\n5.5.1 https://support.google.com/mail/?p=WantAuthError r13-v6sm6514618wmf.35 - gsmtp', 'webmaster#localhost')
enter image description here
If you saved your email/password in environ variable for the first time. Please close your terminal and open it again and run the server, I hope this will solve your problem. I have run into the same problem and solved issues just like this.
it is so cool that you are using stackoverflow. Please look around for already solved issues that are similiar to yours before posting a new question. We should use the resources we already have. (You don't open new gas station everytime you refuel your car, right? ok, sorry for exaggeration, but you get the idea)
what you need in this case is, most of the time, to allow access less secure apps to your gmail account: https://myaccount.google.com/lesssecureapps?pli=1
but in best practice, you should use services that are focused on this. e.g. sendgrid or other email services.
Related
I've been unable to access the Dialogflow console. I've tried logging out and logging back in, clearing site data, using different browsers and incognito mode. I even gave myself Dialogflow admin permissions through Google Cloud Console's IAM.
I've submitted a support request, but waiting on a response. Other folks have asked similar questions on stackoverflow without any response so far. I hope someone can share how to solve this.
You can try to reset your account as indicated in this similar issue from the Public Issue Tracker, specifically follow the steps from comment#2.
If the issue persist, you will need to wait the response from support.
While Isaac's answer here is valid and something that was suggested by the support team as well, the reason turned out to be a change in my email address. The fix was done by Dialogflow's team behind the scenes.
If anyone else faces an issue logging into Dialogflow and have made any change to their email address (including domain) recently, that would be something you would want to convey to Dialogflow's support upfront.
Please, somebody explain me how to create a working Credential Provider! I am using the HardwareEventCredentialProvider sample as a base to build my own Provider on top of. I've changed username and password fields, but it seems doesn't work. After submiting credentials to a system I only see a blank screen for a sec. or receive a message "Incorrect password or username" and then authentication starts again...
What I need to do in GetSerialization() and SetSerialization() methods to log in with existing user?(username=L"virt naXa!", password=L"1234")
I've read "Credential Provider Technical Reference" and Dan Griffin's article about CPs in Vista and still don't understand how can I log in using credential providers. (Maybe I've done it not carefully and need to reread them?)
And I'm sorry for my bad English, it's not my native language:)
It's been awhile since I asked this question...
I remember only that thereat I reread this article (in Russian) and carefully followed the example in order to create my own Credential Provider. And it worked!
Unfortunately, the source codes provided by the author of that article are not available anymore. And here you can find another sample of Credential Provider.
Download the MSDN samples and customize them from here (new link).
they are actually a little bit outdated, but they still do work!
I should first note that I am a newbie in python/django applications but I am trying hard to learn :)
I am working/experimenting on a django project that supports login through openid providers. So I was able to login through my google account with no problems.
Recently, I decided to change the url of my site but at the same time I kept the current database because I dont want to lose my data,users etc. After that point, I am not able to login to the application. This is the following scenario that happens all the time:
Try to login to my site
Site doesn't remember me and I am redirected to google server
I fill my credentials in google server
I am redirected to my site that complains that the user already exists
So, I don't know how to manage with this problem. Is there any workaround or a hack that I can do to my database that will solve this problem? When I browse to my database I find several tables that may be related:
django_authopenid_association, django_authopenid_nonce, django_authopenid_userassociation,django_authopenid_userpasswordqueu
One of the tables in my database (django_authopenid_association) contains the following data. Do you believe that If I reset anything there is going to help?
If you have any good advices/tips are more than welcome.
Thanx
I found a solution/temp hack that worked for me. Of course, this doesn't imply that my solution is the optimal nor that I recommend this to anyone else.
What I did is to create a second account to my application using the same gmail account but having different user name. Then, I edit the new entry in the django_authopenid_association table, copy paste the openid_url value and use it for my old user (database entry 1 in the screenshot of my question).
After that, since I was able to login with my old user, I delete from the database the new user and everything seems to work smoothly until now.
Regarding the django-email-login app, how do i get it not to require email verification by the user? I find that this extra activity that the user has to go through by logging into their email account to validate their email could reduce signups.
I assume you are referring to this django-email-login: https://bitbucket.org/jokull/django-email-login/src, and not my django-email-login: https://bitbucket.org/tino/django-email-login/overview, (sorry for the confusion, I hadn't seen his repo until I bumped into this question and started searching) as I don't do any signup.
However I would like to advice you that you might be more likely to get an answer when you post your question as an issue on bitbucket, as there people that use the app will actually see it.
From a quick look at the code I would say you need to write your own RegistrationBackend, one that doesn't need validation. The backend used in jokull's code is actually the one from django-registration, so you should take that as an example.
I'm working on a django site, which I want the authentication part to work exactly like how Stack Overflow works. A new user comes to the site, they click on "create new account", choose their OpenID provider, get validated, then an account is created for them with "openiduser4356" or something as the username. The user can then go into preferences and change the username to whatever they want. I don't want any kind of local account sign-ups at all.
I pretty much spent all day getting django-authopenid working and it seems the only way this plugin works is by adding OpenID identities to already existing accounts. Heck, you can't even run your site when you have django-authopenid installed unless you have django-registration installed as well...
Before I spend another day wrestling with this thing to try getting it to do what I want, I'd rather just know off the bat if this kind of thing is even possible/a good idea. I noticed that there are a few other OpenID plugins for django out there. Are any of them any better at doing what I'm trying to do?
django-openid does not depend on django-registration.
You might also take a look at a fork of django-openid, django-openid-consumer. It works with the most recent python-openid libraries.
If you don't mind using rpxnow.com, check out http://github.com/howthebodyworks/django-rpx/tree/master