I'd like to connect two different accounts with one Zapier app. I've seen other apps support this but there doesn't seem to be any mention of this in the documentation or be any example apps that do this.
Looking at the auth documentation, there doesn't seem to be an option to pass in multiple authentication handlers:
const App = {
// ...
authentication: authentication
// ...
};
How can I get my app to have the user connect to two separate accounts?
Ah! Good question, I'll try and clear the confusion here.
You do not need to build out any functionality to handle multiple user accounts for your app. Zapier will do this for you. All you need to do is specify how your app authenticates.
Once you push the app, you can go to the connected accounts tab, search for your app and connect multiple user accounts.
One can also add another user account while using the app in a Zap (that rhymed!). Click on connect account and complete the auth.
Hope that helps!
Related
I have a use-case where I need to use apple login on two application (one has a iOS mobile app also) which belong to the same company but have different logos, is it possible to use the same apple login service in both. More specifically I had an issue with apple private relay with hide my email, as the accounts were duplicating on my iCloud profile. Is there way to link those two client_id so they don't create duplicates.
I've checked the apple documentation but it doesn't cover this topic.
I have been looking for documentation or tutorials which show what to do in order to allow a creator (who already has a connect account (it was created when he first authenticated)) to add the banking information necessary for him to withdraw funds from his connect account (transfer his funds).
How app works:
Creator makes an account like on patreon.
User subscribes to creator like on patreon.
How can I allow the express connected account add his details?
Here are some links I have gatherd but don't seem to contain info on how to:
https://stripe.com/docs/connect/express-accounts
https://stripe.com/docs/connect/charges#types
It depends on what type of Account.
Standard Accounts: https://stripe.com/docs/connect/standard-accounts#create-link
Express Accounts: https://stripe.com/docs/connect/express-accounts#create-link
Custom Accounts: https://stripe.com/docs/connect/connect-onboarding
For express accounts redirect users to stripes onboarding
I emailed them for info before I got this answer. I will include their info here:
I understand you would like to know how a user can input their bank account information on the client-side.
As per in docs Stripe will handle onboarding, account management, and identity verification for your platform, which means you can onboard users very quickly. This is done by using the OAuth connection flow, after this, your user will be able to connect to your platform.
You can test this by trying the sample we have using Rocket Rides. Also, here you will be able to find the demo’s source code.
On the other hand, if you are referring to updating this information after the onboarding, this is done by logging on the Express Dashboard, and you can achieve this by integrating with the Express Dashboard.
Extra info: https://stripe.com/connect/express
This is especially helpful: https://stripe.com/docs/connect/collect-then-transfer-guide
My goal is to prevent users of multiple login in. I do not want this to be client-side, with like the onDisconnect and onConnect values, but with a server check. I came across this answer:
How to prevent simultaneous logins of the same user with Firebase?
Which tells me to create a custom auth system. When I am following the docs (https://firebase.google.com/docs/auth/ios/custom-auth) I need to "Copy this file to your authentication server" (3c). How would I do this? I am just using Firebase and my little iOS app. I would like to manage everything on these 2 things, no server in between, is this possible? Or can this file only be uploaded through another server?
If above things are not possible, how can I server check if the user really signed in? I am using Cloud Functions, but I did not came across a trigger for a user signing in. Please no answers with onDisconnect/onConnect, I want it server side. A user may NOT login if he is already logged in. Thanks :)
Implementing custom authentication requires that you have a secure place to mint the custom token that identifies each of your users. You cannot do this securely with only client-side code, because that would mean everyone could claim to be whoever they want.
While you can use Cloud Functions for Firebase to implement a secure back-end without spinning up your own server, I highly recommend against doing that just for the purpose of preventing a user to sign in from multiple locations.
It's important when talking about security to split these two steps:
Authentication - a user proving to be who they are
Authorization - the authenticated user being able to use your app
There very seldom is a reason to keep a user from proving who they are. Your concern seems to fall onto keeping them from using the app from multiple locations. To do that, it's probably easier to track for each user where they are using the app from already using Firebase Database's presence system.
Also see:
How to handle multiple connections of the same user on Firebase?
Android - How to detect same user from multiple devices?
How to prevent same user logging in from different devices ? My app is paid , so I dont want credentials to be shared
I have a dev, stage and production app in a Quickblox account. When testing I'm signing up a new user in production. There are no users in my production app and one user in my staging app.
I'm getting an error saying the external id has already been taken. Looking in the logs I'm definitely connecting to the different apps.
Is this the correct behaviour? Do I have to create a new account if I'm going to be using external ids with multiple apps?
Yes, this is the correct behaviour. User base are shared between all apps, so you can have a line of apps and all users will be able to use the same login+pass to sign in.
To avoid such things you cab create another Admin panel account and use it for dev/qa envs.
I am creating an app with multiple login options.
There will be a possibility to login via Facebook, Google+, and a manual login.
Its all good for now. But lets talk about the case where a user decided to logout from one account, and login using the other account. For instance, logging in via Facebook, logging out, then logging in via Google+.
This scenario causes the database to create multiple users in the database for only one user.
The only way I can think of solving this, is to find a link between all the different logins.
Options:
Email - The user can use different emails for the different apps, or might not have his email public through one of the social apis.
Phone Identifier - The user might let someone else use the app on his phone, or the user might have multiple devices.
Name - There will be many people with identical names.
Due to the above not being viable options, I wanted to see how other people have approached this concern.
I am not looking to use any 3rd party frameworks.
Thanks!