I have three developers. I have try OAuth these three accounts. I can OAuth only to the primary account. For the other two accounts, I got an error message like this:
"sorry we don't recognise your email address"
Thanks in advance
Related
I have a custom developed Windows service that until recently used basic authentication to access an O365 mailbox over POP and pull the contents on a predefined schedule. Microsoft recently announced that they were dropping the support for basic authentication and I should be using OAuth 2 instead. I have followed the steps in this article and my application has the necessary permissions in the Azure portal. I'm still running into an issue.
I can successfully generate the OAuth token. When I try to use said token to authenticate I get "Authentication failure: unknown user name or bad password". No further details are available. I tried Microsoft support but they only referred me to guides I've already followed. Any help is greatly appreciated!
After three days of scratching my head I finally stumbled upon the answer. Turns out that according to Microsoft ObjectID is different from ObjectID. Because logic! Two different interfaces for the same thing with two different ObjectIDs. You need the one on the right when giving permissions to the mailbox.
I have an application that authenticates users via Google Oauth. When I click Signup button, a signup screen would pop up as shown in the figure below.
The problem is that I want users to signup emails with domain name of my organization. Specifically, the username suffix should be #my_organization.com instead of #gmail.com as displayed in the figure. I have tried to modify the Oauth Consent Screen but there seems to be no option to configure this.
as you mentioned the "Sign in with Google" is for login purposes through OAuth protocol when the accounts already exists in an organization, I am afraid this is not intended to delegate user creation since this is a task only domain administrators are allowed within an organization.
The most you can achieve from OAuth is to force the sign in with an specific domain; you can do this by modifying the "hd" parameter in the authentication request you are sending using the Google's OAuth 2.0 API. Here you can check on this topic: click here
As mentioned above, if you are looking to create user accounts with a specific domain you need to be an administrator in a Google Workspace account.
I hope this information helps!
You can only use oAuth with registered Google accounts.
With Google Workspace you can use a domain in your Gmail, see.
But if that's not possible and you want a quick way to authenticate, maybe Auth0 or similar tools can help.
I tried searching multiple forums and documentation but didn't get the answer. I am posting here so that you all fantastic people can answer my question.
Requirement
I am using google OAuth to signup for my application. So when google oAuth opens the email selection screen, I want to enforce or nudge the user to use corporate email instead of using personal email ids (Personal email ids I mean #gmail.com mail ids).
Is there a way (or workaround) I can achieve this?
My company uses Stripe with many of our clients. We have 1 phone number that is linked to all accounts and our team is constantly asking what the 2 step code is to login to Stripe account. Is there a way to connect to Slack so we get codes there versus someone having to manually add to stripe for team member requesting code? Thanks so much!
This may not be possible by Zapier. You will have to do this via https://www.twilio.com/docs/studio/tutorials/how-to-post-sms-to-slack or other services such as https://www.heymarket.com/slack/
We build a product that integrates with DocuSign's API. When the customer connects our product to DocuSign, we surface an OAuth2 login flow to authenticate the integration.
This has been working for most customers, but we've found that when a customer has multiple docusign accounts to choose from, the OAuth2 flow gets stuck and never redirects back to our service.
Flow:
User signs in to DocuSign using their email address
They click "allow" on the permission prompt
Docusign prompts them with the screenshot below (I excluded the email addresses to pick from below the explanation for privacy reasons):
When they select one of the email addresses, the page does not do anything. Are we doing something wrong on our end? Or is this a bug in DocuSign's authentication flow?
That's not the expected behavior. I've reached out to you via LinkedIn with my contact information and would love to take a look at what's going on from the back end.