Skip to content

LG-12190 Store vtr and acr_values in sp_session#10004

Merged
jmhooper merged 11 commits intomainfrom
jmhooper-add-vtr-param
Feb 6, 2024
Merged

LG-12190 Store vtr and acr_values in sp_session#10004
jmhooper merged 11 commits intomainfrom
jmhooper-add-vtr-param

Conversation

@jmhooper
Copy link
Contributor

This commit adds code to the OpenidConnectAuthorizeForm to consume a vtr param. This param validated and then added to the ServiceProviderRequest and eventually added to the sp_session by the StoreSpMetadataInSession service.

This vtr param will eventually be used along with the new AuthnContextResolver tooling to determine what features need to be in place for an authentication and identity proofing transaction.

In #9991 the `vtr` property is added to the `ServiceProviderRequest`. Since the `vtr` property is introduced there it is unsafe to create a `ServiceProviderRequest` record with `vtr` during a deploy since some instances may have code that is unaware of the `vtr` property and will result in an `ArgumentError` when creating a `ServiceProviderRequest`

Once the changes in #9991 are deployed it should be safe to create records with the `vtr` property. This commit does that in the `ServiceProviderRequestProxy`.

[skip changelog]
This commit adds code to the `OpenidConnectAuthorizeForm` to consume a `vtr` param. This param validated and then added to the `ServiceProviderRequest` and eventually added to the `sp_session` by the `StoreSpMetadataInSession` service.

This `vtr` param will eventually be used along with the new `AuthnContextResolver` tooling to determine what features need to be in place for an authentication and identity proofing transaction.

[skip changelog]
theabrad and others added 4 commits January 31, 2024 15:10
Co-authored-by: John Maxwell <john.maxwell@gsa.gov>
Co-authored-by: John Maxwell <john.maxwell@gsa.gov>
@theabrad theabrad marked this pull request as ready for review February 1, 2024 20:04
@theabrad theabrad requested a review from zachmargolis February 1, 2024 20:04
Comment on lines +321 to +322
rescue Vot::Parser::ParseException
nil
Copy link
Contributor

Choose a reason for hiding this comment

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

would we want to catch this exception and add an error for it? or no

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The validate_vtr param has kind of a roundabout way of doing it. It looks like see if the param is present and this is nil.

I would like to find a more direct and elegant way of doing it. The trick with this getting reliably re-evaluated with valid? calls could get messy.

@jmhooper jmhooper force-pushed the jmhooper-write-vtr-to-sp-request branch from a00798f to e03acc8 Compare February 5, 2024 16:36
Base automatically changed from jmhooper-write-vtr-to-sp-request to main February 5, 2024 18:12
@jmhooper jmhooper merged commit 0145c7e into main Feb 6, 2024
@jmhooper jmhooper deleted the jmhooper-add-vtr-param branch February 6, 2024 15:23
jmhooper added a commit that referenced this pull request Feb 6, 2024
jmhooper added a commit that referenced this pull request Feb 6, 2024
jmhooper added a commit that referenced this pull request Feb 6, 2024
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.

3 participants