qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Godfrey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-6990) Support password expiry
Date Wed, 13 Jan 2016 08:57:39 GMT

     [ https://issues.apache.org/jira/browse/QPID-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rob Godfrey updated QPID-6990:
    Attachment: QPID-6990.patch

The attached patch provides a connection validator which checks for expired accounts and defines
a new interface for authentication providers which support expiry.

The SCRAM* providers have been enhanced to support expiry, but provide no way of actually
setting it (though it can be set through the initial configuration).

In addition the REST API and UI will need to change to detect expiry and to redirect to a
password update page on encountering an expired login

> Support password expiry
> -----------------------
>                 Key: QPID-6990
>                 URL: https://issues.apache.org/jira/browse/QPID-6990
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Java Broker
>            Reporter: Keith Wall
>             Fix For: Future
>         Attachments: QPID-6990.patch
> Enhance the Java Broker authentication mechanism so that it supports password expiry.
 For channels that support  changing a password (e.g. management over HTTP) after I login
with a password that needs to be changed, the system should prompt me to change my password,
perhaps disallowing my attempts to do other work until I have do so. 
> The system would support perpetual accounts (typically for application use).  It would
also allow accounts to be created in such a way that they require change on first use.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message