I have a project uploaded on google cloud and on that project whenever some one registers he gets an email saying "welcome".
When this project was hosted on a web server(not google cloud server) it was working fine and emails would go on registration.
But since the project has been moved to google cloud the email services have stopped.All the other functionalities are working fine.
IS there something iam missing out ,or does google want us to get a email domain from google.
coding language- cake php
database - Mysql
I have already unblocked ports 25,587,465 ,but that also did not resolve the issue
Please advise and help.
I think you may have to use SendGrid to use other email than gmail.
As describe in this document:
https://developers.google.com/compute/docs/sending-mail
There are examples listed there as well.
I deployed a relay outside of GCE and configured it to listen on TCP/588 (non standard SMTP port) and then configured all of my GCE instances to relay to that host over TCP/588. That's been working great for months now.
Related
I'm setting up the SMTP server on my keycloak instance.
I tried with my Gmail account, just to see if it works. I generated applications credentials following Google documentation. It worked nicely.
Now, I want to use the SMTP relay mode on my Google Workspace account, which has a specific domain. Google recommends. It works on other apps I have, but I could not make it work with Keycloak. There is no place to put the Domain so I don't even know if it's possible.
I searched the internet. This guy encountered my issue, but I think he solved it by doing it with applications credentials as I did in the beginning.
The thing is, I'd prefer not use application credentials because that would link my app to a Google User. I could create a dedicated one, but it would be a monthly cost. The SMTP relay solution seemed the perfect way, until I could not make it work.
Is there something I miss ? Maybe another way to use Google's SMTP server ?
Thank you for reading
Antoine
Google is getting rid of less secure app access feature. I'm using smtp email service for my website's contact page. But after 30 May, 2022 this service will not work probably.
Is there any other way to give third party less secure app access to my Gmail account ..?
Can an app password solve this problem ..? I have doubts that setting app password will not give access either as google said this may not work for less secure app.
So is there any way to fix this so that the smtp email service works as it should ...?
TLDR:
I had a similar problem, I set up an App Password, and my email-sending piece of code is working fine again.
This video shows how to set up App Password.
Google's formal instructions for setting up an App Password.
Caveats:
Initially, Gmail had automatically turned off my less secure apps setting because I hadn't used that test account in several months. I turned it on, but since I saw the message that it'd be disabled by 2022.05.30, I went ahead and set the app password. This means my current setup has both less secure apps AND app password enabled in my Gmail account, though I'm only using the app password for authentication.
My program usually ran from within WSL2 on top of Windows 11. Even after setting up the app password, my code was returning a gaierror: [Errno -3] Temporary failure in name resolution error when running from within WSL2. I then tried running it straight from Windows 11 and it worked just fine. I now need to fix the networking issue causing this, but it doesn't seem to be directly caused by using app password.
I hope this helps.
Note: 2-factor authentication needed to be enabled before proceeding.
Less secure apps (https://myaccount.google.com/u/0/lesssecureapps) options is deprecated.
We can use apppasswords functionality provided by Google using following link.
https://myaccount.google.com/u/0/apppasswords
Use 16 digit code provided by google instead of password and that should serve as authentication token.
It can be done via 2 factor authentication and app password
I have created a Flutter app with Laravel/MySQL as the backend side.
I've got my api's using the localhost:port .
Everything works fine , using Xampp.
Now , as you may have noticed this my first time trying to deploy my work , how can I deploy my server side(Laravel,MySQL) to any paid service ?
Then, how can I change the api from localhost to an actual address valid everywhere using the app that will be deployed to Google Playstore .
you can use any hosting service like heroku, hostinger, aws basically you can use any and also with that hosting you will get an ip for that hosting and that ip will work every instead of local host.
Yes that ip will also work in google play store app.
Especially if you lack any experience deploying, consider using Laravel Forge https://forge.laravel.com. It is made for Laravel and will massively simplify the deployment and take a lot of configuration needs of your back.
I'm trying to get the Cyberduck CLI (duck.sh) to work interfacing with a google drive (not "Google Cloud Storage") and I'm having problems getting the oAuth authorization to work. I found this thread but it's out of date - as the newer versions of Cyberduck do absolutely work with Google Drive. Using the regular cyberduck GUI I can browse and operate on my G-drive instance, but I can't quite quack the code (sorry!) for how to make this work using the CLI.
[lwobker:~]$ duck -l googledrive://<user>#gmail.com/
Authenticating as <user>…
OAuth2 Authentication. Paste the authentication code from your web browser.
Authentication Code: <pasted pass here>
Save password (y/n): n
Disconnecting www.googleapis.com…
Login failed. Malformed auth code. Please contact your web hosting service provider for assistance.
I've tried a number of different URLs, including:
#gmail.com
me#gmail.com#www.googleapis.com
and a couple of others.
I also can't seem to figure out where the GUI version of cyberduck stores it's authorized credentials... if I could re-use those that would be fine, doing a one-time setup at the beginning doesn't break my use case.
I'm somewhat familiar with the Google Developers API, and I've created one for use with this project, but I can't seem to figure out how the Google "Client ID" and other credentials map to the Cyberduck tool.
Make sure you paste the auth code obtained from the Google login page opened exactly as is without any line breaks. More information is available in the wiki.
I'm new to Federation Services and I'm trying to understand how ADFS works as a whole and I've started to get down into the details. I followed along with creating an app using OIDC to authenticate a user, however, within the tutorial, they specified using a "Server Application" when setting up an Application Group. This ended up not working for me so I tried setting up a "Native Application" application group for kicks and was able to successfully login.
The thing that threw me off is, I ended up hosting ADFS on a server outside of the domain in which I had my application running, so I'm confused as to how that is "native" in terms of ADFS.
I went looking for this answer within microsoft's documentation but I didn't find the information very clear.
Native Application:
"Sometimes called a public client, this is intended to be a client app that runs on a pc or device and with which the user interacts."
Server Application:
"A web application that runs on a server and is generally accessible to users via a browser. Because it is capable of maintaining its own client 'secret' or credential, it is sometimes called a confidential client."
This may seem simple to some, but I'm trying to really get a grip on what would be used when. To me it sounds like a native application is used when you're running the application natively on a pc in which the user is also using the same pc, and the server application is run remotely in which the user would not be using the same machine. Is it really that simple or am I misunderstanding?
A native application (in Microsoft speak) is something that is not browser based e.g. mobile. The code runs client side. It may use JavaScript in which case the secret key is publicly accessible. (The secret key is one of the OAuth parameters). You use ADAL / MSAL to access it.
A server application runs server side e.g a web API. The secret key is not publicly accessible. You use OWIN to access it.
These terms have no relevance to where ADFS is actually installed. Native applications typically are not domain joined.