MongoDB Atlas
Britive integrates with MongoDB Atlas through the Britive Access Broker and the Atlas Administration API. At checkout, the broker calls the Atlas API to create a temporary database user. At checkin, the user is deleted — no standing database accounts exist between sessions.
This is a true zero-standing-privilege (ZSP) pattern: there are no permanent database credentials to rotate, leak, or forget to revoke.
Access Patterns
- Temporary database user — creates an Atlas database user with a specified role at checkout; deletes the user at checkin. Supports any Atlas built-in or custom role.
The broker communicates outbound to Britive over HTTPS and to the Atlas API over HTTPS — no inbound ports are required on the broker host.
In This Section
- Getting Started
Set up the Britive Access Broker for zero-standing-privilege access to MongoDB Atlas — create an Atlas API key, configure the broker, and register your Atlas project as a resource.
- Temporary Database User
Create and delete MongoDB Atlas database users at checkout and checkin via the Atlas Administration API — zero permanent credentials.