Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

1. Identity management departments at Higher Ed institutions have many different ways to provide testing accounts and identities for their application developers. These range from "just test in production" to more complex strategies. Can you please describe how your institution approaches this problem? (check boxes)

  • Our application developers test with our production identity environment and we don't have a separate test identity environment.
  • We have a test environment that is a complete copy of our production identities.
  • We have a test environment that consists only of randomly generated identities and does not contain any real identity information.
  • Other (comment box)

...

3. Sometimes problems or bugs arise which can only be solved in the production environment. How does your institution handle this type of situation? (check boxes or radio buttons)

  • We will allow a developer to "take over" someone else's identity.
  • We create a separate, new identity in production for the developer to use. (please describe)
  • We allow a developer to alter their own identity in order to do their troubleshooting (or we will do this for the developer) - e.g. change their type from staff to student. (please describe)
  • We have a "set" of identities in production that developers can use. (please describe)
  • Other (comment box)

...

7. Any other comments, ideas or issues you would like to see discussed with respect to identity management test entities?

  • Comment box

Thank you for participating!