Testing with Auth Armor is easy. Because there are no credit cards, payment info, or anything that is a permanent and altering action, we recommend you create a test project alongside your production project. Your production environment will have far more users than your test/dev/uat environments. You can set them up the same to ensure you have aligned settings. Then simply create new API keys and use them in your environment testing, just as you would a connection string to a database or other service.
Create as many projects as you need to align with your own needs. Remember, only active users are billed, so even in the event you create thousands of users during testing, your testing bill would only incur for those that initiated an auth event, and only for that month the user was active.
Updated about 2 months ago