Authentication Requirements

Use Cases

1. NAMED SUBSET OF MIT COMMUNITY: Standard Administrative Applications
   1. UNSECURE PORT: If user tries to enter the application via a non-SSL (unsecure) port then the application should display a page that does the following:
      1. Display a statement saying that this application requires a client certificate
      2. Displays a link to tell the user how to obtain an MIT issued certificate.
      3. Gives the user the SSL version of url for them click
   2. NO CERTIFICATE: If the user tries to enter the application via the SSL (secure) port and the user does NOT have a valid MIT issued client side certificate then the user should be routed to the non-SSL port in (1) above.
   3. NO AUTHORIZATIONS: If the user has a valid client certificate but does not have ANY authorizations for this particular application then the application should display a page that tells user who to contact to get the required authorization.
   4. VALID USER: If the user has a valid client certificate AND at least one authorization for this particular application then the user should be allowed into the application.
   5. SWITCHING: If the user first comes in via the SSL port then switches to the unsecure port the application should detect this present the same situation as (1) above.
   6. MIDDLE OF APPLICATION: If a valid user first comes into the application at some url that is NOT the main entry point for the application the programmer needs the OPTION to be able to prevent this and to route the user to the main entry point instead.
   7. IMPERSONATE: If the user has a valid client certificate PLUS a special "impersonate" authorization and the user goes to a special impersonate entry point then the user should be prompted for the person whom they wish to impersonate.

...