qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-6922) Trying to edit shipped authentication provider 'passwordFile' leads to 404
Date Tue, 01 Dec 2015 12:55:11 GMT

    [ https://issues.apache.org/jira/browse/QPID-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033640#comment-15033640

ASF subversion and git services commented on QPID-6922:

Commit 1717415 from orudyy@apache.org in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1717415 ]

QPID-6922: [Web Management UI] Fix defect causing error during edit of authentication provider
Merged from trunk with command:
svn merge -c r1717401 https://svn.apache.org/repos/asf/qpid/java/trunk

> Trying to edit shipped authentication provider 'passwordFile' leads to 404
> --------------------------------------------------------------------------
>                 Key: QPID-6922
>                 URL: https://issues.apache.org/jira/browse/QPID-6922
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>            Reporter: Keith Wall
>            Assignee: Keith Wall
>            Priority: Minor
>             Fix For: qpid-java-6.1
> Steps to reproduce (qpid-java-6.0 RC2):
> # Open management console
> # Navigate to authentication provider {{passwordFile}}
> # Click 'Edit'
> # Dialogue box appears
> # Click Save without making changes
> # Dialogue box disappears  DEFECT: Error message "404 - Object with name 'passwordFile'
does not exist!" appears
> Analysis shows that the dialogue actually causes two updates.  It is the second update
that fails.  It appears that the location of the second request is badly constructed.  It
includes the name of the authentication provider rather than the name of the preference provider.
> https://localhost:8080/api/latest/preferencesprovider/passwordFile/passwordFile
> Any changes made to the authentication provider path are saved properly.  Changes to
preference provide can be made by the separate edit dialogue.
> Any newly created authentication provider will have a preference provide named after
the authentication provider, so the defect will not manifest.

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