You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/04/14 14:08:25 UTC

[jira] [Created] (QPID-7198) LDAP and OAUTH2 Authentication Providers should cache authentication results for a short period

Keith Wall created QPID-7198:
--------------------------------

             Summary: LDAP and OAUTH2 Authentication Providers should cache authentication results for a short period
                 Key: QPID-7198
                 URL: https://issues.apache.org/jira/browse/QPID-7198
             Project: Qpid
          Issue Type: Improvement
          Components: Java Broker
            Reporter: Keith Wall


The OAUTTH2 and LDAP authentication providers should be changed to cache authentication results for a short (configurable period).  If the same authentication provider receives the same credentials again (i.e. matching username and password), it should reuse the cached authentication result.   The cached authentication result should expire automatically.

This would serve to reduce load on authentication backends (such as Directories).  It will be especially useful when the REST API to used for programmatically monitoring the Broker which otherwise may create an excessive load on the backend.

The authentication provider must not retain the user passwords in clear.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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