What are live credentials when working with accounts? I've done some searching and can't find an answer.
The following image is from the Plaid API Docs: https://plaid.com/docs/quickstart/
Test you integration with live credentials means you can test the real bank account in the development environment. In development, you can test max 100 real bank accounts (Live credentials) for testing purpose. After 100 accounts, you can test anymore real accounts in development.
So do your testing in sandbox environment with test credentials(user_good, pass_good) for the banks and once you are confident about your integration switch to development and test with real bank accounts.
https://dashboard.plaid.com/overview
Sandbox - Use test credentials and account data to build out and test your Plaid integration
Development - Test your Plaid integration with real credentials and account data for up to 100 Items
Production - Connect unlimited bank accounts and access our full range of products; all requests are billed
Note : You need to request plaid for development access for your keys.
Like the list indicates, there are multiple environments. The sandbox environment uses example (mock) credentials (referred to as 'test credentials'), while the development environment uses actual credentials (referred to as 'live credentials'). Live in this sense means credentials that can actually be used, hence why you need to request access.
Related
I need developer account on Amazon Seller Central so I can work with their API. It needs adding credit card and it shows $39.90 monthly fee, that is so much money for me. Is there option to make free developer account or sandbox to test Amazon API??
Yes, there is a free option to test Amazon's API. It's called the "Amazon MWS Sandbox." The sandbox environment allows you to test your application's integration with Amazon's Marketplace Web Service (MWS) without incurring any charges. You can use the sandbox to test your code, verify that it's working correctly, and debug any issues before you switch to live data. To get started, sign up for a sandbox account on the Amazon MWS Developer Documentation page.
My mac brokedown.Thus, I can't use the touchID to verify myself anymore on heroku. Thus, the only other option is to use 1-time password generator which I don't even have it setup & you need to login (and verify) to be able to setup. What shall I do? How can I gain access to my heroku account?
Heroku recommends having a back-up in place:
We recommend registering another verification method to ensure that you can log in to Heroku on other devices where a built-in authenticator is not present.
and:
Recovery codes provide an important backup if your usual MFA verification method is not available. For example, if you normally use Salesforce Authenticator but forget your mobile phone one day, you can still log in using a recovery code. Generate a list of ten single-use recovery codes that you can keep in a safe place until you need them.
This is always a good idea when using MFA with any service.
If you do not have another authentication method registered and you don't have recovery codes, you'll have to ask for help. How you do that depends on whether you're a member of an enterprise account:
Registering multiple MFA verification methods is strongly recommended.
If you’re a member of a Heroku Enterprise Account and need help with recovering access when your MFA verification method isn’t available:
Your Enterprise Account admin can generate a temporary verification code that allows you to log in to your account (starting August 2021)
You can contact support for help.
If you're not a member of a Heroku Enterprise Account:
e-mail account-lockout#heroku.com for help.
We may request additional information to recover access to ensure that an attacker is not attempting to access your account.
I'm using a Google Service Account to push MySQL backups from our webserver to Google Drive using a Google API PHP client script setup as a cron job.
I now want to run the same script across multiple webservers, I'm not sure how to correctly configure the service account for this, should I?
Use the same service account and service account key/credentials across all servers?
OR Use the same service account, but add a service account key/credentials for each server?
OR Setup a separate service account for each server?
Your requirements/needs/whatever may vary, but this generally it won't wont matter how you do it.
Single project
Create a project on Google developer console, and create a single service account key file and share it across the servers.
Is the same as.
Creating a project on google developer console and creating three separate service account credentials with different key files.
You will be bound by the same quota limits because all are under the same project.
Three separate projects.
Now if you created three different projects and create a single service account credential for each of the different servers. Then you would see a difference as they are different projects so should be bound by different quota limits.
quota
The Google drive default quota is so high anyway i'm not sure that it really matters what you do.
Security
Even security wise if you have a different file and you were hacked on one server you would't gain or loose anything by the other servers not having the same or different key files.
Google started the OAuth developer verification process a few months back which forces the developers having OAuth applications to apply for verifications if they don't want their users to see a warning screen and to have an unlimited number of users using the OAuth flow.
I'm facing a problem due to this verification process when I have to use the projects in a local environment. There is no way I can verify the apps for local environments since the policies and T&Cs cannot be hosted.
Q1. Is there any way to skip the verification process and sandbox the OAuth application?
Q2. What is the exact limit for the accounts? (Since I use 5-10 Gmail accounts, but do multiple signups per day from those accounts and I still hit the limit quite often)
Q1. Is there any way to skip the verification process and sandbox the OAuth application?
If you check the side of the consent screen it answers some of your questions.
you can learn more here
Q2. What is the exact limit for the accounts? (Since I use 5-10 Gmail accounts, but do multiple signups per day from those accounts and I still hit the limit quite often)
If you add these accounts as users on the project in the developer console they should be able to use it while you are testing.
I am developing an app that uses Directory API to create user accounts within Google Apps for Work. I have been testing this on a Free (legacy) account but now I need to test adding and removing domains, which Free account doesn't support. I don't want to get a paid account just yet and rack up a huge bill by adding and removing accounts in testing. I also don't see a way to get a sandbox/developer account to test this out. How can I accomplish this?