You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, it's not possible to change the bceid_business_name in the app. When we create a user, we get bceid_business_name from the session in the FE and send it to the endpoint to put into the db. When we update a user, we send the same information from the FE, but the UserUpdateIn ninja schema strips out session. So the db never receives the updated business name.
If someone needed to change their BCEID business name, the process could look something like this:
user contacts Service BC to get the business name changed for the BCEID
we put bceid_business_name into UserUpdateIn
user logs into the app once Service BC has changed the name and their session ~should have the new business name
user goes to the profile page and submits. There's no field for business BCEID name that they can change, but when they submit, that sends the session info and their name is updated.
BCEID business name should now be updated in the app (check by looking at the user access requests grid as a CAS user)
Acceptance Criteria
first
second
third
Definition of Done
first
second
third
Additional context
Add any other context about the task here.
Or here
The text was updated successfully, but these errors were encountered:
Describe the task
Currently, it's not possible to change the
bceid_business_name
in the app. When we create a user, we getbceid_business_name
from the session in the FE and send it to the endpoint to put into the db. When we update a user, we send the same information from the FE, but theUserUpdateIn
ninja schema strips out session. So the db never receives the updated business name.If someone needed to change their BCEID business name, the process could look something like this:
bceid_business_name
intoUserUpdateIn
Acceptance Criteria
Definition of Done
Additional context
The text was updated successfully, but these errors were encountered: