looking for advice on testing in an SSO environment

Does anyone care to share how they allow users to test in an SSO environment? The basic problem, of course, is that the folder won't always be availabe to them and they can't login as someone else.

Tagged:

Comments

  • Hi Tom,

     

    There is always the opportunity for one oor more users to have rights to change todo lists for users.  We have admin forms for special Super User group and they manage  this in case someone has the folder not on the todo list already.

     

    I hope this helps.

     

    Best regards

    Sascha

  • We have disabled SSO on test machines and all developers can login into web-client with any credentials.

  • Most if not all of our customers will use SSO only in production with standard logins being used in development and test environments. This does seems to be the normally accepted practice in my experience. Of course it depends how many environments you have at your disposal.

  • Your other option would be to use both SSO and standard authentication scripts (with SSO having priority) thus allowing users who fail SSO authentication to authenticate using a standard login. You will need to make sure though that the user who is testing cannot be authenticated via SSO - this would normally mean not setting them up as a user in Metastorm although it does depend on how you have configured SSO to work.

     

    Hope this helps.