Now that we have a setup for local development that does not require the use of localtest by instead hybriding into At22, we have a much more easily available setup. However, if the AT environment is down or if one for some reason cannot access it (eks due to IP restrictions) we might need an alternative solution.
For this, the BFF mock can be expanded upon to run our UI purely with the BFF mock. All we need is some way to log in and create the necessary cookie (see setup in localtest)
Tasks for data setup:
[ ] Create a simple view that contains a dropdown list over different users, preferably based on the BFF mock data
[ ] Make that view only show up when enabled in appsettings.development
[ ] Make cookie based on response from this endpoint and change the url based on what's chosen in the views:
https://altinn-testtools-token-generator.azurewebsites.net/api/GetEnterpriseToken?env=at22&scopes=altinn:resourceregistry/resource.admin&org=ttd&orgNo=991825827&ttl=36000
Cookie that's going to be made:
[ ] See localtest subdomain for other things that should be added
Description
Now that we have a setup for local development that does not require the use of localtest by instead hybriding into At22, we have a much more easily available setup. However, if the AT environment is down or if one for some reason cannot access it (eks due to IP restrictions) we might need an alternative solution.
For this, the BFF mock can be expanded upon to run our UI purely with the BFF mock. All we need is some way to log in and create the necessary cookie (see setup in localtest)
Tasks for data setup:
https://altinn-testtools-token-generator.azurewebsites.net/api/GetEnterpriseToken?env=at22&scopes=altinn:resourceregistry/resource.admin&org=ttd&orgNo=991825827&ttl=36000Cookie that's going to be made:Additional Information
No response
Tasks
No response
Acceptance Criterias
No response