Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Technical feasibility assessment of CA mDL for Cal-ITP Benefits #2765

Open
4 tasks
indexing opened this issue Mar 18, 2025 · 1 comment
Open
4 tasks

Technical feasibility assessment of CA mDL for Cal-ITP Benefits #2765

indexing opened this issue Mar 18, 2025 · 1 comment
Labels
deliverable Work that ends with a non-code deliverable (e.g. Google doc)

Comments

@indexing
Copy link
Member

Assess the technical feasibility of supporting CA mDL as a method to verify rider identity and eligibility for certain enrollment pathways in Cal-ITP Benefits.

Use case

This is the use case they highlight that enlightened me:

  1. Secure Login for DMV Services
  • Individual goes to CA DMV website to start a process that requires them to log into their CA DMV website account.
  • The current process requires them to use a username and password, which can be forgotten or stolen.
    A new option, with the individual’s consent, uses the CA DMV App to log in using a much more secure mechanism than using a username and password.
  • This helps provide more security around the individual’s account and how they manage their CA DMV related activities.

Questions

  • Because this functionality in open source, can we can integrate it into the Benefits app without additional agreements with the DMV (e.g the authority to operate)?
  • What attributes are available for the Benefits app to use to verify eligibility for transit benefits (e.g. date of birth). I'm especially curious if they offer Veteran or Veteran disability status, as well as general disability status.
  • What is the t-shirt size level of effort to complete the integration?
  • Any areas of particular concern that introduce risk in supporting this integration?
@indexing indexing added the deliverable Work that ends with a non-code deliverable (e.g. Google doc) label Mar 18, 2025
@indexing indexing added product Issue captures work for the product team and removed product Issue captures work for the product team labels Mar 18, 2025
@indexing
Copy link
Member Author

cc// @thekaveman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deliverable Work that ends with a non-code deliverable (e.g. Google doc)
Projects
Status: Todo
Development

No branches or pull requests

1 participant