Skip to content

Deploy RC 445 to Production#11778

Merged
jmdembe merged 16 commits intostages/prodfrom
stages/rc-2025-01-21
Jan 21, 2025
Merged

Deploy RC 445 to Production#11778
jmdembe merged 16 commits intostages/prodfrom
stages/rc-2025-01-21

Conversation

@jmdembe
Copy link
Contributor

@jmdembe jmdembe commented Jan 21, 2025

User-Facing Improvements

  • Accessibility: Improve step indicator legibility at high text zoom levels (#11758)

Internal

  • AAMVA: Hardens AAMVA maintenance window definitions and test coverage (#11753)
  • CI: Fix job that checks pinpoint config (#11772)
  • Dependencies: Update dependencies to latest versions (#11761)
  • Doc Auth Socure: Add config variable for maximum allowed socure users (#11755)
  • Email: Create client pool and retry instance profile credentials when sending emails via SES (#11765)
  • Error Reporting: Do not report LexisNexis or AAMVA exceptions to NewRelic (#11760)
  • Feature Flags: Fix feature flag checks so that they allow subdomains of identitysandbox.gov. (#11767)
  • IdV flow: Simplify creation of Idv::ProofingComponents (#11742)
  • In-person Proofing: Remove in_person_full_address_entry_enabled feature flag usage. (LG-14958 #11746) (#11746)
  • Localization: Improve reliability of JavaScript string extraction (#11775)
  • Maintenance: Move Faker gem from all environments to test (#11757)

Upcoming Features

  • Document Authentication: AB vendor buckteing should default to configured default doc auth vendor (#11764)
  • Identity Verification: Socure timeout provides hybrid users with options. (#11734)
  • Requestable attributes: A claim that will allows SPs to request the user's UI locale was added (#11756)

Mitchell Henke and others added 16 commits January 16, 2025 08:19
changelog: Internal, Maintenance, Move Faker gem from all environments to test
…#11755)

changelog: Internal, Doc Auth Socure, add config variable for maximum allowed socure users
changelog: Internal, Error Reporting, Do not report LexisNexis or AAMVA exceptions to NewRelic
We have a service provider who would like to be able to receive the user's UI locale when they receive attributes after sign in. This partner has a `post_idv_follow_up_url` value that is configured to redirect the user to Login.gov with a request for verified attributes. Since the user does not see a UI on their site and likely does not have an established session there they want to know what locale the user is using on Login.gov to provide a consistent experience.

This commit enables partners to request to user's locale using the `locale` OIDC scope. The locale is stored in the session and set to the current user's locale on every request. This ensures the latest value will be returned to service providers.

changelog: Upcoming features, Requestable attributes, A claim that will allows SPs to request the user's UI locale was added
Bumps [libphonenumber-js](https://gitlab.com/catamphetamine/libphonenumber-js) from 1.11.17 to 1.11.18.
- [Changelog](https://gitlab.com/catamphetamine/libphonenumber-js/blob/master/CHANGELOG.md)
- [Commits](https://gitlab.com/catamphetamine/libphonenumber-js/compare/v1.11.17...v1.11.18)

---
updated-dependencies:
- dependency-name: libphonenumber-js
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
LG-15337: Try again page for hybrid mobile flow

If the system times out waiting for the data from Socure,
show the try again page with, if available, an option to switch to
in person proofing.

changelog: Upcoming Features, Identity Verification, Socure timeout provides hybrid users with options.

* working Try Again feature spec
* failing feature spec for opting in to IPP from socure hybrid timeout
* allows direct to IPP in hybrid flow
* fix the IPP `Back` link redirect back to Socure timeout page
* Back link from IPP correctly returns to timeout page in both standard and hybrid flows

---------

Co-authored-by: John Maxwell <john.maxwell@gsa.gov>
Co-authored-by: Gina Yamada <gina.yamada@gsa.gov>
Enhances test coverage for AamvaStateMaintenanceWindow

Previously, an invalid key could break the proofer. This expands test coverage, and also improves the maintenance window code itself to harden against that.

changelog: Internal, AAMVA, Hardens AAMVA maintenance window definitions and test coverage
…doc auth vendor (#11764)

* the default bucket for AB doc auth vendor shoudld the configured default doc auth vendor
changelog: Upcoming Featgures, Document Authentication, AB vendor buckteing should default to configured default doc auth vendor

* spec for default bucket during AB vendor routing

* changelog: Upcoming Featgures, Document Authentication, AB vendor buckteing should default to configured default doc auth vendor
When the browser's text zoom level is very high, the step indicator steps can become very crowded.

This commit adds a min-width to individual steps that is based on the root font size to prevent this issue.

changelog: User-Facing Improvements, Accessibility, Improve step indicator legibility at high text zoom levels
* Tweak how local cert is generated

- Don't include port in CN
- Add SAN including the IP address (required for Safari on iOS)

[skip changelog]

* Update docs for local development

- Bind to a specific IP
- Describe how to trust cert on iOS

* Don't include port number in name of SSL cert files

This will ensure new keys / certs are generated without requiring folks to remove the old ones first.
**Why**
* Currently, we compute the vendor for remote document verification
  using DocAuthRouter, which requires downstream business logic to
  depend on context that may or may not be available. In order to
  eliminate calls to DocAuthRouter in places like Idv::ProofingComponents,
  we first need to start storing the vendor directly in Idv::Session.

**How**

* Add a new key `doc_auth_vendor` to Idv::Session.
* Set the new key after successful document capture. If the user opted
  for in person proofing, it will be `usps` (managed directly in `Idv::InPerson::StateIdController`), otherwise we use the
  existing `Idv::DocAuthVendorConcern#doc_auth_vendor` method.
* Clear `Idv::Session#doc_auth_vendor` if the following steps are undone: link_sent,
  document_capture, and socure_document_capture, and ipp_state_id.

changelog: Internal, IdV flow, Simplify creation of Idv::ProofingComponents
* Retry instance profile credentials when sending emails via SES

changelog: Internal, Email, Create client pool and retry instance profile credentials when sending emails via SES

* add instance profile credential retries to pinpoint
* allow subdomains of identitysandbox.gov to work

* changelog: Internal, Feature Flags, Fix feature flag checks so that they allow subdomains of identitysandbox.gov.

* make lint happy

* Update lib/feature_management.rb

Co-authored-by: Mitchell Henke <mitchell.henke@gsa.gov>

* be more specific with the domains

* ruby syntax is funny

* make rubocop happy

---------

Co-authored-by: Mitchell Henke <mitchell.henke@gsa.gov>
changelog: Internal, Localization, Improve reliability of JavaScript string extraction
Error:
  $ if [ "$CI_JOB_STATUS" != "success" ]; then
  /bin/bash: eval: line 215: unexpected EOF while looking for matching `"'

changelog: Internal, CI, Fix job that checks pinpoint config
@jmdembe jmdembe merged commit e42909e into stages/prod Jan 21, 2025
@jmdembe jmdembe deleted the stages/rc-2025-01-21 branch January 21, 2025 18:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.