Reason Pattern Matching Validation in Access Workflows

Common Fate now supports reason pattern matching validation in access workflows.

This feature allows administrators to set up more sophisticated rules for access requests, ensuring that provided reasons meet specific criteria or patterns.

For example, administrators can now validate that reasons include specific formats (like JIRA ticket IDs) or enforce minimum length requirements for provided reasons.

Advanced Filtering for Access Requests

Common Fate has significantly enhanced the filtering capabilities on both the Requests and My Requests pages. Users can now apply a range of new filters to quickly find the information they need. These new filters include:

• Grant count filtering to sort requests based on the number of associated grants.
• Manual or auto approval filtering to distinguish between requests that went through manual review and those approved automatically.
  
• Time range filtering for key events in the request lifecycle, including when requests were submitted, approved, and closed.
  

Improved Transparency for Access Request Closures

Users will now find attached reasons describing why access request grants were closed. This addition provides clearer insights as to why a request was closed, such as activation period expiry or access duration expiry.

Improvements

• Added the ability to specify an override for the RDS endpoint per RDS user, allowing read roles to use a read-only replica endpoint.
• Fixed an issue where access requests with many entitlements attached would not deprovision correctly.
• Fixed a performance issue which could cause the Availability Maker background job to fail.
  
• Removed the assign public IP feature on the control plane for improved security.

‍