Testing authenticate-dashboard-user.featureScenario: IdP user without credentials attempts login (Charlie)
Test executes correctly for all steps, with minor issue on the last step:
And Charlie is presented with an "Access Denied" page informing them to contact their administrator
Currently, all that is presented is a standard Nginx "forbidden" message. This is adequate for now, but as we move into Pilots this may be confusing for users. If their IT department has failed to give them entitlements they requested (preservation-user or preservation-admin), they may think there is a technical issue. Some explanation of what to do, who to contact etc. (along with whatever branding / visual style guides should be in place) would help users resolve their issue.
Testing authenticate-dashboard-user.feature
Scenario: IdP user without credentials attempts login (Charlie)Test executes correctly for all steps, with minor issue on the last step:
And Charlie is presented with an "Access Denied" page informing them to contact their administratorCurrently, all that is presented is a standard Nginx "forbidden" message. This is adequate for now, but as we move into Pilots this may be confusing for users. If their IT department has failed to give them entitlements they requested (preservation-user or preservation-admin), they may think there is a technical issue. Some explanation of what to do, who to contact etc. (along with whatever branding / visual style guides should be in place) would help users resolve their issue.