You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2013/04/02 23:45:16 UTC

[jira] [Updated] (QPID-4691) [Java Broker] update web UI handling of SSL attributes and make the broker validate port attributes more closely to avoid illegal configurations which prevent start-up

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

Robbie Gemmell updated QPID-4691:
---------------------------------

    Summary: [Java Broker] update web UI handling of SSL attributes and make the broker validate port attributes more closely to avoid illegal configurations which prevent start-up  (was: [Java Broker] update web UI handling of SSL attribites and make the broker validate port attributes more closely to avoid illegal configurations which prevent start-up)
    
> [Java Broker] update web UI handling of SSL attributes and make the broker validate port attributes more closely to avoid illegal configurations which prevent start-up
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-4691
>                 URL: https://issues.apache.org/jira/browse/QPID-4691
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: 0.21, 0.22
>            Reporter: Alex Rudyy
>            Assignee: Robbie Gemmell
>            Priority: Critical
>             Fix For: 0.23
>
>
> On setting of broker attributes the keystore/trustore/peerstore attributes only validated when path is changed. As result, when password or alias is changed no validation happens and invalid values can be stored.
> On setting of port attributes only attribute types are validated. As result if SSL port is configured without keystore or need/wantClientAuthorisation. attributes are set without truststore the following broker start fails as broker cannot bind to SSL port without keystore/truststore accordingly.
> The web management port UI should allow the setting of need/wantClientAuthorisation attributes only when SSL transport is selected.
> Broker UI to edit keystore/trustore/perrstore password should not require the setting of the password every time when path to keystore/trustore/perrstore is changed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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