Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-416

User.forcePasswordChange, and user expiration should become part of the core API

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Ready for Work
    • Priority: Should
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Complexity:
      Medium

      Description

      On the 25-Feb-2010 dev call, inspired by ticket TRUNK-451 we decided that saying a User needs to change their password (possibly including account expiration) needs to be part of the core API. If your password is disabled/expired, you should not be able to do anything in the system, even in a non-web context.

      (This is related to past discussions on adding a user status that's richer than just having User.retired.)

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            darius Darius Jazayeri
            Votes:
            4 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: