How do you control access to your staging/QA/preview environments?
Hello!
I'm working on an idea and I'm interested in learning about everyone's experience protecting (basic auth, VPN, etc.) non-production environments - staging/QA/test/preview.
What have you used? Were there any pain points such as sharing credentials, rotating credentials, or providing access to others?
Appreciate the time!
Mostly just put a server password like with .htpasswd + .htaccess
Hey @orliesaurus! Thanks for the response. Do you manage multiple usernames/passwords with htpasswd? Do you have to share credentials with others?
Usually 1 per project...I share the password with the people I want to access my front-end!
@orliesaurus if you were able to easily manage access in a central place without having to create or share passwords, would that be something you'd be interested in? Think easy SSO (single-sign on) for these environments.
This comment was deleted 3 years ago