-
Notifications
You must be signed in to change notification settings - Fork 17
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
Create RO Picker Design to replace Caseflow login screen #2272
Comments
@gnakm what should the error state be if the server has an error when the user clicks the "login" button? |
@NickHeiner Great question! I was just about to ask you what are the potential errors in this situation. I have this generic one. If you can tell me more in detail what is happening in the backend, that would be helpful. Other wise, if this works please give it a thumbs up and I will add it to the AC above. AC
🥃 📋 |
@NickHeiner Let me know if you want ^^the above to be a separate issue. |
Nah, I'll do it in this PR. Thanks! |
I don't think that a more specific error message is needed. |
Now that VACOLS is going to 2FA, we shouldn't be using VACOLS credentials to disambiguate the which RO the user is in. Connect #2272.
PASSED
|
Ticket cloned from https://github.com/department-of-veterans-affairs/appeals-design-research/issues/248.
Context
VACOLS is moving to 2 factor authentication on June 10th (earliest) or mid-July. When this happens, users at ROs that have more than 1 VACOLS RO ID to their 1 VBMS Station ID will not be able to access Caseflow. Caseflow login screen currently tries to use their VACOLS login to log into VACOLS. But with 2FA we will be prevented from doing that. 😱
AC
h1
and instruction is in lead paragraph Style guide text stylingMock up
Copy
Welcome to Caseflow!
Please select the Regional Office site you are logging in from
Reference
List of VBMS Station IDs and VACOLS RO IDs:
https://github.com/department-of-veterans-affairs/caseflow/blob/master/app/models/vacols/regional_office.rb
The text was updated successfully, but these errors were encountered: