...
- 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)
4. What doesn't work about your current test environment?
- Comment box
5. Many application developers use their desktops for initial development, then move on to a test environment, and then move on to production. Do you provide any special identities for the "development" environment (as opposed to "test" and "production")?
- Yes (please describe)
- No
- Other (comment box)
65. At least one institution has created a "test" attribute in their production directory which is used to indicate that an entry is not a real identity. Do you think it would be useful to have an attribute like that available as part of the eduperson schema?
- Yes, we would use something like that.
- No, we probably wouldn't be interested.
- Comments
6. What doesn't work about your current test environment?
- Comment box
7. Any other comments, ideas or issues you would like to see discussed with respect to identity management test entities?
...