Skip to content

Conversation

@yanshengzhangHMRC
Copy link
Contributor

No description provided.

updatedUa <- Future.fromTry(ua.set(AgentClientsPage, updatedList))
_ <- sessionRepository.set(updatedUa)
} yield AgentLandingViewModel(
clientName = updatedClient.schemeName.getOrElse(""),
Copy link
Contributor

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?

Copy link
Contributor Author

@yanshengzhangHMRC yanshengzhangHMRC Nov 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

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)
Copy link
Contributor

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 ?

Copy link
Contributor Author

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.

jassalrichy
jassalrichy previously approved these changes Nov 26, 2025
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Richy, updated now

@platops-pr-bot
Copy link

Copy link
Contributor

@jamalosman jamalosman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants