{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"user":{"avatar_url":"https://secure.gravatar.com/avatar/02e7748709d84ea0cddf018520a569c1?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"02e7748709d84ea0cddf018520a569c1","url":"https://api.github.com/users/intrica","login":"intrica","id":569687},"milestone":null,"labels":[{"name":"nice to have","color":"02d7e1","url":"https://api.github.com/repos/NoamB/sorcery/labels/nice+to+have"}],"updated_at":"2011-11-04T03:42:25Z","assignee":null,"closed_at":null,"comments":2,"url":"https://api.github.com/repos/NoamB/sorcery/issues/141","body":"It would be nice to have a module feature that allowed the definition of whether a user is active (or archive/inactive)\r\n\r\nWhen users are \"removed\" from our system, their accounts stay in existence and are flagged as inactive in order to maintain audit logs etc... It will be nice to just specify a boolean attribute that reflects whether a user is active/inactive.","html_url":"https://github.com/NoamB/sorcery/issues/141","title":"Ignore inactive or archived users","number":141,"id":2140417,"created_at":"2011-11-04T03:05:28Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/02e7748709d84ea0cddf018520a569c1?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"02e7748709d84ea0cddf018520a569c1","url":"https://api.github.com/users/intrica","login":"intrica","id":569687},"updated_at":"2011-11-04T03:42:25Z","url":"https://api.github.com/repos/NoamB/sorcery/issues/comments/2626977","body":"Thanks for your response. Although I did consider this. It's a messy solution as the whole point of the activation module is to allow users to activate their account. This seems a very hacky way of simply disabling an account from an administrative situation, or if indeed accounts expire etc...\r\n\r\nI'm not sure what would prevent the user from activating their account in your example? This seems a very basic use case for users and accounts. I point you towards managing accounts on a Windows domain, or most CRM systems. Both have a way for administrators to simply disable the account without removing it.\r\n\r\nI agree that I'm not looking for the is_active? method. This is simple to implement if that were to solve the issue.\r\n\r\nJust for clarity, I see the activation submodule as a way to require activation of an account. I'm looking for a way to disable/deactivate an account as an administrator. I don't see this as a nice to have. I see it as a requirement for any serious user authentication system.","id":2626977,"created_at":"2011-11-04T03:42:25Z"}}