# Generating asserted login id in Sandbox environment **URL:** \ **Category:** NHS login\ **Tags:** authentication, onboarding, nhs-app-api\ **Created:** [24 October 2023 12:37 UTC](https://developer.community.nhs.uk/t/generating-asserted-login-id-in-sandbox-environment/540 "2023-10-24T12:37:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![anna.weaver](https://avatars.discourse-cdn.com/v4/letter/a/e99b99/32.png) [@anna.weaver](https://developer.community.nhs.uk/u/anna.weaver)\ **Post date:** [24 October 2023 12:37 UTC](https://developer.community.nhs.uk/t/generating-asserted-login-id-in-sandbox-environment/540/1 "2023-10-24T12:37:39Z")
We are building an App that will eventually be accessed form teh NHS App - so we have authentication using an asserted login id. Onboarding to the app is taking longer than we hoped and we have a mock NHS App frontend that we use to test the authorisation journey - we had been copying and pasting an asserted login Id from the mock site but have been asked to connect to NHS login instead. I can get all that working and get back access tokens - but what I would like to do is build an asserted login id so we can leave the App code as it is. Is this possible - and, if it is, can anyone point me to documentation for how to do it. I have tried the solution used for the Hello world app - it did not get me where I needed to be. ---
**Author:** ![darren.hutton](https://avatars.discourse-cdn.com/v4/letter/d/0ea827/32.png) [@darren.hutton](https://developer.community.nhs.uk/u/darren.hutton)\ **Post date:** [3 November 2023 12:36 UTC](https://developer.community.nhs.uk/t/generating-asserted-login-id-in-sandbox-environment/540/2 "2023-11-03T12:36:25Z")
> [@anna.weaver](#): > > but have been asked to connect to NHS login instead Hi Anna. Are you integrated with NHS login now? And having done that I’m assuming you can trigger a flow where a user logs in, but what you’re trying to do is keep your auth flow as live like as possible?