Bugs in new improved onboarding workflow (request acces)

Need help? Ask here! Bug & Error Reports
1

Which tool versions are you using?

Platform: v26.04.4

I really like the new onboarding improvements which definitely helps the onboarding workflow. Apart from not having to retype stuff (roll, name etc.), I also like that all admins now get a notification email. However I see that there are some improvements, which (for me) seem to be bugs.

Current Behavior

  1. the notification email has a line: <USER> is requesting access to the VIKTOR VIKTOR environment.

I think ‘VIKTOR VIKTOR’ should be replaced by the name of the actual environment that is requested. I’m managing multiple environments and it is kind of hard to see which environment they are requesting acces for (apart from hovering over the link and clicking the link)

  1. The button approve all should not be visible in an SSO environment. –> Acces should be done via the identity provider, and by clicking the ‘approve all’ the user gets an email that the user has to set up a password –> this is confusing because the password will not work. Either the solution is too have no button, OR the button should only tell the user: you are successfully added (and no prompt to setup a password)

image
image1653×217 13.4 KB

Expected Behavior

  1. replace VIKTOR VIKTOR by the actual evironment name (which is setted in the settings/appearence/page title?)
  2. hide the button, or change the behavior for SSO environments.
2

Hi Wichard,

Thank you for taking the time to provide this feedback. On the two points:

  1. This will be fixed with next week’s release
  2. We designed the access requests page for admins for two types of logins: one managed by the VIKTOR admin (normal credentials authentication), and the other by the identity provider admin (SSO). The SSO case should simply be a to-do list for the VIKTOR admin to take action by contacting the identity provider. We overlook the part where the admin, after having taken action, then can remove the entry, if they wish to (the entry also disappears once the user actually enters the environment). Therefore, we will remove the button, and allow the admin to remove the entry if they wish to. This will be released the following week.
1 Like
3

elaborating on:

  1. I agree that the ‘tasklist’ idea is great, especially when multiple admins are managing the accounts and have an easy list to check if someone already took action. So it seems that ‘task completed’ (or removing an entry) is a great fix.
4

Is this released already? The view ‘acces requests’ is getting cluttered with entries that I cannot cleanup (people that are NOT and will NOT be added)).