I was able to use gMail (or Hangouts）account in Pidgin client a couple weeks ago. But lately, I got the "Not Authorized" message every time I tried to connect to my gMail account from Pidgin client.
Wondering if something has been changed, or connecting from Pidgin client to gMail (Hangouts) account is not supported anymore.
Here is the config in pidgin client:
In Basic tab:
Protocol: XMPP
Username: gmail account name (without #gmail.com)
Domain: gmail.com
Resource: Empty or gmail.com
Password: password for password
In Advanced tab:
Connection Security: tried all available options
Connect port: 5222
Connect server: talk.google.com
File transfer proxies:
Same issue here. According to https://support.google.com/a/answer/49147 perhaps they simply shut down Google Talk already; Hangouts and Chat do not support XMPP. You can try to use the native plugin https://bitbucket.org/EionRobb/purple-hangouts/wiki/Home
Related
I am using the paho-mqtt library in my frontend and want to connect to my MQTT Broker which is running on my backend. I created one user account for the broker.
One way to connect to the broker is by using the username, the password and the mqtt.connect(options) function.
But this means that the username and password will be in the frontend in clear text which I have to avoid, because somebody could try to get the username and password somehow and connect to the broker - this should never happen. only users who successfully logged in should be able to connect to the broker.
How can I solve this?
Thanks for your help and all the best,
Kevin
Without knowing what broker you are using this is going to be hard to answer. I'm also assuming that when you say frontend you mean a web app and you are using the Paho Javascript client in the page to connect to the broker?
But assuming you are using a broker that supports some sort of authentication plugin/API then it will be trivial to dynamically create a username/token when the user logs into the frontend and using these to authenticate to the broker. The credentials can be passed to the page as part of the login process and used to authenticate the page, when the session expires or the user logs out then you delete these generated credentials rendering them useless.
I have an application which sends an email if an error occurs. I am using gmail account as from and to address. But when I run my program it gives me authentication required error. I got an email from google saying Sign-In attempt prevented. I also signed in for app password but it just worked once. When I see the apps connected to my account, the list is empty. How can connect app to my gmail account? How can I have this application access gmail account to send email.
You can try to use the SMTP server of GMail to send e-mails.
SMTP server address: smtp.gmail.com
SMTP user name: Your full Gmail address (e.g. example#gmail.com)
SMTP password: Your Gmail password
With Gmail 2-step authentication enabled, use an application-specific Gmail password.
SMTP port (TLS): 587
SMTP port (SSL): 465
SMTP TLS/SSL required: yes
You can let your application access your Gmail account by turning on "Access for less secure apps" to lower the security level.
It's a setting on the "My Account" page under Sign-in security. The link https://www.google.com/settings/security/lesssecureapps should take you there.
We are having issues with Connect notifications from our DocuSign demo account.We are not able to receive any updates from our Connect configuration. Though, when I republished the XML from Connect logs, I did receive a Connect update to a specified URL.
When I created new envelopes using API as well as from DocuSign account itself, I never got any notifications to the same URL.I do not even see a Connect log.
We do not have any issues with Connect notifications for our DocuSign live account.
We have never experienced this issue before with Connect updates from our DocuSign demo account.
Please advise.
Just a hunch - do you use http or https? connect can only work over port 443 with a valid SSL certificate. If you're on localhost - you may need to get a temp certificate or something like that but also using azure websites is good way to avoid this issue since they're pretty much just as good as working on your localhost
I am able to run Google's sample code for Gmail IMAP/SMTP using JavaMail with oAuth on cmdline (OAuth2Authenticator.java from http://code.google.com/p/google-mail-oauth2-tools/)
But the same code doesn't seem to work for SMTP (IMAP works fine) in the web app on tomcat. It throws
535-5.7.1 Username and Password not accepted. Learn more at
535 5.7.1 http://support.google.com/mail/bin/answer.py?answer=14257
Any idea, why this doesn't work for SMTP alone on web app?
Recently I turned my gmail account into 2-step verification ON.Now when I try to connect my gmail account through any jabber(xmpp supported) clients.. it wont work.I know gmail is based on xmpp protocol.Does xmpp protocol support 2step verification or its a different set of process.. please let me know.
XMPP still should work. You will be required to generate a application password for each client (e.g. XMPP client, phone, etc.).
http://support.google.com/accounts/bin/answer.py?hl=en&answer=185833