We have switched to the latest version of the SOAP APIs of Tuleap "5.8.99.12" deployed on demo.tuleap.net with the fix for "TrackerWorkflowRuleArray is referenced but not defined" but we are facing another issue.

In some part of our code that we have not changed in the last two months we now have an error which seems returned by the server:

AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: Call to undefined method Tracker::userCanAdmin()
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:Call to undefined method Tracker::userCanAdmin()

Step used to produce the problem:
1- (using the "common" wsdl) login(name, password)
2- retrieve the session hash from the session returned
3- (using the "tracker" wsdl) getTrackerList(session_hash, groupdId)
4- (using the "tracker" wsdl) getTrackerFields(session_hash, groupId, tracker_id)
5- (using the "tracker" wsdl) getTrackerStructure(session_hash, groupId, tracker_id)

During the steps 1 to 4, everything is working nicely and we can retrieve the name of the group, the name of the tracker, the list of the fields etc. When we are running the step n°5, to retrieve the information about the semantic and the workflow of the tracker, the error appears. We've checked on our side and we don't have any operation named "userCanAdmin()" or any admin-related operation.

The test has been performed on our project on demo.tuleap.net (https://demo.tuleap.net/projects/obeo groupId=141, trackerId=484) and I am an admin of the project in question. I even tried to change the permission on the tracker to specify that "project admins" are also "admin of the tracker" with no effect. Ultimately, since the SOAP API may even be used by unregistered users, should we modify something special on our tracker to give them the rights necessary to manipulate the tracker?