Exclude agent service accounts from seat counting
What does this MR do and why?
This MR exludes any service accounts created for agents from being counted towards the namespace's seat count. This ensures that service accounts used for Duo agents and integrations do not impact the billing based on user seats.
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
- Create a number of service accounts on the GDK using rails console (using premium license)
- Once the service account exceeds the seat count you should see an error
- Update one of the service accounts with
composite_identity_enforced = true - You should now be able to create a new service account.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Shekhar Patnaik