-
Notifications
You must be signed in to change notification settings - Fork 1
DTR-1170: Wiring in LP-2 #28
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
base: main
Are you sure you want to change the base?
Conversation
| updatedUa <- Future.fromTry(ua.set(AgentClientsPage, updatedList)) | ||
| _ <- sessionRepository.set(updatedUa) | ||
| } yield AgentLandingViewModel( | ||
| clientName = updatedClient.schemeName.getOrElse(""), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just want to check, should the clientName be the schemeName?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so as per confirmation from Laiba before, link for above pic is F6
| GET /agent/no-client-list controllers.agent.FailedToRetrieveClientController.onPageLoad() | ||
| GET /agent/no-authorised-clients controllers.agent.NoAuthorisedClientsController.onPageLoad() | ||
| GET /agent/authorised-client-manage-CIS-returns controllers.agent.AgentLandingController.onPageLoad() | ||
| GET /agent/cis-return-dashboard/:uniqueId controllers.agent.AgentLandingController.onPageLoad(uniqueId: String) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our we ok to expose the uniqueId in the url ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding uniqueId as we need something that distinguish different agent clients. If we don't want uniqueId exposed in url, we can refactor the code to use index as we have all agent clients persisted in Mongo.
From the security side, I assume this should be fine. If the agent changes the uniqueId in the url from "123" (authorised) to "456"(unauthorised), we still have the guard in BE to ensure that only client authorised agent can view the landing page for a certain client. So agent would not see client's landing page whose uniqueId is "456".
Also uniqueId is not itself PII like utr or NINO or other sensitive info like tax office no. & ref that are actually exposed in the url in the as-is java service.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we create a component simial to:
https://github.com/hmrc/customs-financials-secure-messaging-frontend/blob/main/app/views/GovukWrapper.scala.html#L66
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Richy, updated now
|
jamalosman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
No description provided.