Hi Fernando,
I’m not sure that I understand what you try to do, please could you explain how the result should be?
You used the Tamino security in the right way. Tamino authentication is done by the web server and Tamino does authorisation with its ACL/ACE and group concept.
With Tamino WebDav it looks a little bit different. The Tamino WebDav server uses the Tamino security for protecting its metadata and the Tamino collections used via the WebDav server against parallel or not authorised accesses. Authorised is just the WebDav server itself. For this we defined an user, group and ACL especially for the Webdav server and just this user should have write access to the metadata collection and all the collections used via webdav in Tamino. Because of the webdav server has not to be authenticated, the authentication at the web server should not be activated. If you would like to use authentication with Webdav, you have to use the authentication of your servlet engine e.g. Tomcat. The WebDav specification defines authorisation in its sub-specifiaction ‘WebDav access control protocol’, which is in a ‘draft’ status currently and so the Tamino WebDav server does not support it , especially the http ACL method, in the current version.
regards
Eckehard
#API-Management#webMethods#Tamino