Impersonation - was designed for testing, may have other uses.
*In essence, there's a field in Roles that says they can impersonate within a particular application.
*With a separate login screen, the person can then impersonate any user within the the given app.
*This is very useful for testing
*There are also times when a professor might want to see an application from the pov of a particular student.
*kerberos also has methods of doing this, but many systems on campus are not built to use them
*Other use-cases for impersonations?
*Needs to be handled in coordination with IdM projects
Rollout
*Documentation wiki, separate from project wiki
*Developers.mit.edu site.
**Janet working on migration
**features - point to various project notebooks
**deploy apps onto Servers run by MAP, w/ sash stack. Costs?
***Join MAP, get support.
***Audiences - those who want it, those who play, those who are looking farther forward.
***machine costs, and support costs?
***dev server free, production servers cost?
**With a good case to present, costs may be acceptable to IS&T
Kuali
Stewart Brown might serve as an extra pair of hands.
Mark Wiklund - Documentation hands?