webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

Tamino 4.4.1 WebDAV security configuration question

  • 1.  Tamino 4.4.1 WebDAV security configuration question

    Posted Mon October 17, 2005 03:57 PM
    1. enable security in Tamino via SMH 2. make the following ACL request:
    ACL /tamino/welcome_4_4_1/ino:dav/ino:dav/test HTTP/1.1 Host:localhost Content-Type: text/xml Content-Length:649 Authorization: Basic XXX <?xml version="1.0" encoding="UTF-8" ?> <D:acl xmlns:D="DAV:"> <D:ace> <D:principal> <D:href>/tamino/welcome_4_4_1/ino:dav/ino:davPrincipal/ino:user/DOMAIN\user</D:href> </D:principal> <D:grant> <D:privilege><D:read/></D:privilege> <D:privilege><D:write/></D:privilege> </D:grant> </D:ace> <D:ace> <D:principal> <D:property><D:owner/></D:property> </D:principal> <D:grant> <D:privilege><D:administer/></D:privilege> </D:grant> </D:ace> <D:ace> <D:principal><D:all/></D:principal> <D:grant> <D:privilege><D:read/></D:privilege> </D:grant> </D:ace> </D:acl>
    1. receve the following error:
    HTTP/1.1 400 Bad Request Date: Thu, 13 Oct 2005 17:56:53 GMT Server: Apache/2.0.54 (Win32) X-INO-returnvalue: 8552 X-INO-Version: 4.4.1.1 Content-Length: 0 Connection: close Content-Type: text/plain

    The request is taken as is from the book by Lisa Dusseault, page 348 :wink: A quick search on 8552 in the Tamino Documentation finds this page: file:///C:/Program%20Files/Software%20AG/Tamino/Tamino%204.4.1.1/Documentation/en/xprog/xprspstr.htm#spyanchor0 that says

    Any idea what went wrong?


    #webMethods
    #API-Management
    #Tamino


  • 2.  RE: Tamino 4.4.1 WebDAV security configuration question

    Posted Mon October 17, 2005 07:03 PM

    OK, the ace that triggers the error comes here:

     <D:ace> <D:principal> <D:property><D:owner/></D:property> </D:principal> <D:grant> <D:privilege><D:administer/></D:privilege> </D:grant> </D:ace>

    That is, the following ACL works:

    ACL /tamino/welcome_4_4_1/ino:dav/ino:dav/test HTTP/1.1 Host:localhost Content-Type: text/xml Content-Length:649 Authorization: Basic XXX <?xml version="1.0" encoding="UTF-8" ?> <D:acl xmlns:D="DAV:"> <D:ace> <D:principal> <D:href>/tamino/welcome_4_4_1/ino:dav/ino:davPrincipal/ino:user/DOMAIN\user</D:href> </D:principal> <D:grant> <D:privilege><D:read/></D:privilege> <D:privilege><D:write/></D:privilege> </D:grant> </D:ace> <D:ace> <D:principal><D:all/></D:principal> <D:grant> <D:privilege><D:read/></D:privilege> </D:grant> </D:ace> </D:acl>

    Now, whether I try to log in as a DOMAIN\user or as a DOMAIN\anyotheruser, I can write to the folder test. Given that the WebDAV from Tamino 4.4.1 does not support inverted principals, I have no clue about how to deny access to DOMAIN\anyotheruser. P.S. The Security Manager in SMH contains an OS Domain with the option Accept Users = “all”.


    #webMethods
    #API-Management
    #Tamino


  • 3.  RE: Tamino 4.4.1 WebDAV security configuration question

    Posted Tue October 18, 2005 03:01 PM

    Extra info: We decided to retest with two OS Domains and the option Accept Users = “defined” by preforming the following steps: 1. recreated the Tamino DB 2. Added 2 Security os Domains 3. Set

    &#8249;?xml version="1.0" encoding="UTF-8" ?&#8250; &#8249;D:acl xmlns:D="DAV:"&#8250; &#8249;D:ace&#8250; &#8249;D:principal&#8250; &#8249;D:href&#8250;/tamino/test/ino:dav/ino:davPrincipal/ino:user/DOMAIN\user&#8249;/D:href&#8250; &#8249;/D:principal&#8250; &#8249;D:grant&#8250; &#8249;D:privilege&#8250;&#8249;D:all/&#8250;&#8249;/D:privilege&#8250; &#8249;/D:grant&#8250; &#8249;/D:ace&#8250; &#8249;D:ace&#8250; &#8249;D:principal&#8250;&#8249;D:all/&#8250;&#8249;/D:principal&#8250; &#8249;D:grant&#8250; &#8249;D:privilege&#8250;&#8249;D:read/&#8250;&#8249;/D:privilege&#8250; &#8249;/D:grant&#8250; &#8249;/D:ace&#8250; &#8249;/D:acl&#8250;

    on the root of the WebDAV repository /tamino/test/ino:dav/ino:dav 4. Then, we activated the Security by setting authentication to “tamino” 5. restarted ther Tamino DB 4. and we could not log into WebDAV with DOMAIN\user nor with any other DOMAIN user. All authentication attempts results in the 403 Access denied response.


    #Tamino
    #webMethods
    #API-Management


Related Content