Support high assurance level#545
Open
bheesham wants to merge 3 commits into
Open
Conversation
There was a problem hiding this comment.
Pull request overview
Adds support for a stricter authenticator assurance policy (HIGH) in the accessRules Auth0 Action, along with Terraform secret wiring and test updates, to enable RPs to require stronger MFA characteristics.
Changes:
- Introduces an AAL→AAI mapping (including
HIGH) and updates decision logic to select the highest AAL across matching authorization rules. - Updates Duo configuration handling to select credentials based on the required AAL.
- Adjusts Jest tests to reflect new
HIGHbehavior (Duo treated as satisfyingHARDWARE).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
tf/actions/accessRules.js |
Adds HIGH AAL support, mapping/selection logic, and Duo config selection changes. |
tf/tests/accessRules.test.js |
Updates tests for the new HIGH behavior expectations. |
tf/actions.tf |
Renames/splits Duo Action secrets into medium/high variants for the Action runtime. |
Comments suppressed due to low confidence (1)
tf/actions/accessRules.js:382
- For LDAP (
strategy === "ad") users that require Duo,enableDuois set butaairemains empty. That causes MEDIUM requirements to fail the AAI check (sinceAAI_MAPPING["MEDIUM"]is non-empty), denying access before the Duo challenge can be triggered. If enabling Duo is intended to satisfy MEDIUM, add the relevant AAI indicator(s) whenenableDuois set.
// Allow certain LDAP service accounts to fake their MFA. For all other LDAPi accounts, enforce MFA
if (event.connection.strategy === "ad") {
// No support for HIGH or MAXIMUM assurance levels.
if (mfaBypassAccounts.includes(event.user.email)) {
console.log(
`LDAP service account (${event.user.email}) is allowed to bypass MFA`
);
aai.add("2FA");
} else {
enableDuo = true;
console.log(
`duosecurity: ${event.user.email} is in LDAP and requires 2FA check`
);
}
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
bheesham
force-pushed
the
assurance-levels-support-high
branch
from
July 6, 2026 20:17
93e70b5 to
3116de6
Compare
kgowrabathuni
approved these changes
Jul 7, 2026
Jira: IAM-1989
This commit redoes a bit of the logic and expands the test case to allow `HARDWARE`. Jira: IAM-1989
This commit configures the Duo client differently, depending on the level of assurance we want. The client we use has different policies applied, restricting the kind of access required. Jira: IAM-1989
bheesham
force-pushed
the
assurance-levels-support-high
branch
from
July 13, 2026 14:57
3116de6 to
e00eede
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira: IAM-1989
tl;dr: for some RPs we need to support a stricter policy for MFA. This PR adds support for
HIGH.