Team

Susan Brooker-Gross(error), Mary Dunker(tick), Daniel Fisher (tick), Karen Herrington(error), Kim Homer(error), Greg Kroll(tick), Joyce Landreth(tick), Randy Marchany(error), Kevin Rooney(tick), Nate Smith(error), Brenda van Gelder (tick)
((tick) present, (error) absent)

Agenda

  1. July & August 2010 meeting planning. Who is out on what dates?
  2. Discuss account "states".
  3. Review & discuss Requirements Analysis

Meeting Notes


  1. July & August 2010 meeting planning. Who is out on what dates?
    • UCS unavailable mornings for the month of July -- due to NSO
    • Mary unavailable week of August 23rd
    • Daniel - nothing scheduled
    • Greg - out the week of July 12th
    • Joyce - out August 11,12,13
    • Randy - out week of June 28th; July 6,7,8; week of July 19th; July 26,27,28; week of August 2nd; August 9,10,11
    • Kevin - nothing scheduled
    • Note: if possible, please send a representative in your place when you are unavailable.
  2. Discuss account "states"
    • See PID Account States
    • Need to discuss and map-out the correct work-flow for appropriate account states, e.g., when an account is in a "locked" state.
    • "Locked" state
      1. Resetting a locked account will depend on the reason the account is locked.
      2. IMS can lock accounts; 4Help can lock an account by resetting the password; there are programmatic processes that can lock an account
      3. If an account is in a locked state we need to inform the user they are locked and need to contact IMS.
      4. 4Help could configure Remedy to send an e-mail to a user who called for a password reset reminding them that the temporary password expires in 24 hours and if not changed will lock the account.
      5. The only time 4Help can unlock a locked account is if the 24 hour period has elapsed on a password reset.
      6. To avoid the possibility of someone setting their self-service password reset preference to something like do not allow reset over the phone, with an account using a temporary password we would have to check the expiration date of the password which is set when the password is reset.
    • The next few meetings may need a smaller group to discuss possible use cases. Use cases need to be fleshed out for possible exceptions. A representative from the ITSO is highly desirable.
  3. Review & discuss Requirements Analysis
    • See the Requirements Analysis space for added notes.
    • There was a discussion about the "Agreed Upon Authentication Methods" and what methods are acceptable in combination with another method. Several people had a problem with #7 "Email ticket to 3rd party email address" even in combination with anything.
      • Action item: The ITSO needs to "weigh in" on option #7.
  • No labels