How do I migrate my existing App projects/clients (preserving the same client id, secret and all associated data) from one email address to another.
Background: One of our apps was created on a standard gmail account but now we would like to host it on a company email address. We would not like to prompt the user to reaccept terms they've already agreed to.
In the gmail account add the company email address as an owner. It will give full access. If you want to can remove the gmail account and the company email address will take over ownership.
Related
I was just recently created as a new user in Microsoft 365 Admin Center (https://admin.microsoft.com/) and during account creation, when setting up password, there was a field to send the password /setup details to me through another email address (my previous email address, outside O365).
I received my new account notification at this other email address, and now this email address gets notifications etc. but when we look at my Azure AD membership, I can't find where this email address is configured in the settings. Where is this forwarding address being stored?
We checked Azure Admin portal (portal.azure.com) Authentication contact info for my entry and it's not filled in.
It's not in Manage User Name or contact information in the https://admin.microsoft.com/Adminportal/Home#/users page
It's not in my account profile anywhere in https://portal.office.com/account/#personalinfo
Totally stumped! Apologies if the answer is obvious.
Mystery solved: The forwarding was happening through billing notifications setup:
https://admin.microsoft.com/AdminPortal/Home#/BillingNotifications
did you check in the account profile under security and privacy? there is an email field there as well. https://portal.office.com/account/#security
if not there. then there is a different spot,
make sure you're logged into portal.office.com
then go here
https://myaccount.microsoft.com/
then click security info. enter your password again, and there is a authentication email there as well.
hope this is what you're looking for.
Every developer in my company has one email address. eg: Name#country.domain.com
But they also have a domain address/name Name#country.domain.net(hereby refereed as DN)
This is causing a lot of confusion
One is used as email(.com) while the other is not, even-though they both look like emails
Some applications use DN to provide access, some applications use email address to provide access
Some developers country changed, they decided not to change the email which was okay for network admin. But the DN had to be changed to the correct country they are in. Why is it mandatory for domain address to change the country while email can remain as it is?
Due to the last problem #3, we had to find the applications that use DN and update them all.
Here are some more questions:
Why this is email address and then a DN, why cant there be only one?
What exactly is the purpose of DN?
Does every user need to have this(or just developers)?
The abbreviation "DN" refers to the distinguishedName attribute in AD. It also uniquely identifies the account, but it is not what you're talking about here.
What you're talking about is the userPrincipalName attribute (or UPN). It is usually the "username" (sAMAccountName attribute) followed by # and the DNS domain name of the AD domain. It sounds like that is how your organization is setup. Since the accounts moved domains, the domain portion of the UPN needs to change.
However, technically, the UPN suffix (the domain portion) can be anything, especially any domain that your organization controls. It could even be set the same as the email address, it just doesn't have to be.
So if the UPN in your organization does not match the email address, then either your admins just haven't put the effort into making that happen, or they have a reason for not doing so.
You cannot authenticate to AD directly with an email address. If an application just asks for an email and password and using that to authenticate against AD, then it would have to look up that email address on the domain to find the username and then use the username (either sAMAccountName or userPrincipalName) to authenticate.
There is some more reading here that might help: User Naming Attributes
How to replace the randomly generated email address from salesforce with my email address in the email coming from Salesforce. Please find the attached screenshot for better understanding.
Follow these steps
You can define and manage organization-wide addresses for each user profile. When sending email from Salesforce, users with these profiles can select their own address or the organization-wide address for the email’s From address. Replies are delivered to selected address.
REQUIRED USER PERMISSIONS
USER PERMISSIONS NEEDED
To modify organization-wide addresses: Modify All Data
Available in: Lightning Experience and Salesforce Classic
Available in: All Editions
From Setup, enter Organization-Wide Addresses in the Quick Find box, then select Organization-Wide Addresses.
To manage organization-wide addresses, use the available options.
To use an organization-wide address, send an email from Salesforce and choose your organization-wide address from the dropdown list.
The "user" submodule in Google App Engine uses "Google Account" rather than a "G+" sign-in. Are the base ID's the same? I'd like to associate their sign-ins with my own user records...
If you are asking the about the ids...
Specifically:
using
user = users.get_current_user()
returns a user object and that is not what you are referring (regarding to your comment)
The user_id() is what you where reffereing to for the users api:
user = users.get_current_user()
user.user_id()
From the Docs
If the email address is associated with a Google account, user_id returns the unique permanent ID of the user, a str. This ID is always the same for the user regardless of whether the user changes her email address.
If the email address is not associated with a Google account, user_id returns None.
Now from my experience my GoogleID according to user_id() is xxx8005350796570706xx and my Google Plus profile ID is 102445631084043565507 which are totally different. I also checked this with my apps and Google + known followers and found no similarity.
I would say they are not the same thing, but yes, you can associate them.
If you have used the support built into GAE (or Android) for basic Google accounts (User) to authenticate a user then you have their e-mail address which uniquely identifies their google account.
On Google+, use the email scope to gain access to their e-mail address:
https://developers.google.com/+/api/oauth#email-scopes
These e-mail addresses should match, so this will allow you to associate the Google and Google+ accounts. The downside to this method IMO is if you weren't already requesting the g+ email scope then you will have to add it.
You should create an own user model which will have info about registered users. Using users.get_current_user() you may take an e-mail address from user google account and login him to an app.
How do I send email from Google App Engine with a random, non-app admin sender using a custom domain name (e.g. xyz#myshop.com ) ? We need to allow the users of our website to communicate with each other through a custom made messaging system but also allow them to reply directly from their email. Something similar with the craigslist system. However seems that GAE doesn't allow us to send email from an address that is not admin. Is there any workaround / patch ? We are the owner of myshop.com domain name (verified through google apps) so I don't see why a such thing is not allowed.
While you can't use just any random address, you can use a registered administrator address with a '+' suffix. So you could send the mail with a 'from' of, say, message-reply+HASH_VALUE#myshop.com. Then your app will receive the reply, and can use the hash to decide which user to forward the mail to.
How about sending the email from your admin account, but adding a reply-to header, specifying the user's email-address?
Google doesn't allow to use random addresses. You can star this bug.
http://code.google.com/p/googleappengine/issues/detail?id=3069
However, since the users are apparently registered with Google Apps, the system can send emails on their behalf when they are signed into your application.
The sender address must be one of the following types:
...
The address of the user for the current request signed in with a
Google Account. You can determine the current user's email address
with the Users API. The user's account must be a Gmail account, or be
on a domain managed by Google Apps.
http://code.google.com/appengine/docs/python/mail/emailmessagefields.html