[jira] Commented: (MRM-1231) Not authorized to use method with version parameter

["Fabien (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRM-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188260#action_188260 ] 

Fabien commented on MRM-1231:
-----------------------------

No, I have put the logger in Debug mode , but nothing in Archiva logs... If someone can try with the sample client 

>  Not authorized to use method with version parameter
> ----------------------------------------------------
>
>                 Key: MRM-1231
>                 URL: http://jira.codehaus.org/browse/MRM-1231
>             Project: Archiva
>          Issue Type: Bug
>          Components: xmlrpc
>    Affects Versions: 1.2.1
>         Environment: xml-rpc client developed in php
>            Reporter: Fabien
>
> I have instantiated an xml-rpc client in php (which is working) with login / password of archiva administrator account.
> But I have a strange behavior.
> According to this documentation :
> http://archiva.apache.org/docs/1.2.1/adminguide/web-services.html
> I can use Administration Service, and get back information.
> I can use Search Service, excepted methods that are using a version of artifact in parameter!
> For example :
> SearchService.getArtifactVersions( String groupId, String artifactId )  is working
> AdministrationService.getAllManagedRepositories() is working
> SearchService.getDependencies( String groupId, String artifactId, String version ) is not working, And the returned message is : "Not authorized".
> SearchService.getDependencyTree( String groupId, String artifactId, String version )  is not working, And the returned message is : "Not authorized".
> I don't understand my mistake because there is no problem with administration Service which needs an user with System Administrator role in Archiva, but it is not working for Search Services with an artifact version, which needs only an user with at least a Repository Observer role. So for me it's a bug

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira