Skip to content

Support biometric ACR values in SAML#11013

Merged
vrajmohan merged 1 commit intomainfrom
support-biometric-acr-in-saml
Aug 2, 2024
Merged

Support biometric ACR values in SAML#11013
vrajmohan merged 1 commit intomainfrom
support-biometric-acr-in-saml

Conversation

@vrajmohan
Copy link
Contributor

changelog: Upcoming Features, IdV with Biometric Comparison, Supporting biometric acr in SAML

🎫 Ticket

https://gitlab.login.gov/lg-people/lg-people-appdev/Melba/backlog-fy24/-/issues/44

📜 Testing Plan

The testing plan should be similar to what was done for OIDC - https://docs.google.com/document/d/1_TJBdEiErT460qoJh-jiw9E3mlPCffguMn28--4LJK8/edit

@vrajmohan vrajmohan requested review from Sgtpluck and lmgeorge July 31, 2024 20:43
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(nothing needed for this PR, mentioning)

ok so I can't believe I am figuring this out today, but I think it's a really weird pattern the way we assign the transient asserted_attributes to the user object like this, I would love to live in a world where we refactor how we pass the user attributes around, but that seems like not the right idea for this PR right this moment

Copy link
Contributor Author

@vrajmohan vrajmohan Jul 31, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, I am planning to dig into why we have this strange pattern if I have some time at the end.

@vrajmohan vrajmohan force-pushed the support-biometric-acr-in-saml branch from 0bb24b8 to d0e342a Compare August 1, 2024 22:49
@vrajmohan vrajmohan marked this pull request as ready for review August 2, 2024 02:16
Copy link
Contributor

@Sgtpluck Sgtpluck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some minor suggestions and questions, but it looks good! i'll mark it as approved because i think you can move forward with these minor edits

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not a huge deal, but part of the reason for memoization is to make an application more efficient. the resolve method is doing the bulk of the work. did you consider memoizing resolved_authn_context_result along with authn_context_resolver as it's called multiple times?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I considered it. When vtr is not present, which is most of the time, it would be using acr_result which is memoized.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same suggestion as noted above about memoizing this value

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto

changelog: Upcoming Features, IdV with Biometric Comparison, Supporting biometric acr in SAML

1. Updated AttributeAsserter to send correct ial
3. Renamed AuthnContextResolver#resolve to AuthnContextResolver#result
   and memoized it
3. Moved asserted_ial_value from OpenidConnectUserInfoPresenter to AuthnContextResolver
4. Used common asserted_ial_acr method from both AttributeAsserter and
   OpenidConnectUserInfoPresenter
@vrajmohan vrajmohan force-pushed the support-biometric-acr-in-saml branch from e8f1677 to 294c49f Compare August 2, 2024 19:19
@vrajmohan vrajmohan merged commit 8b736a2 into main Aug 2, 2024
@vrajmohan vrajmohan deleted the support-biometric-acr-in-saml branch August 2, 2024 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants