About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Question & Answer
Question
What are the requirements for proxying the PUT and DELETE methods to a back-end server
Answer
To pass the request to the server behind WebSEAL you can look into these options:
1.- Use a Transparent Path junction
2.- Make sure WebSEAL will first attempt to pass the request to a junction using JMT (junction mapping table) or the IV_JCT cookie, before processing the request on the root junction (which is typically on the local file system). This is done using the "process-root-requests = never" option
In order to allow the creation and deletion of objects, you will also need to ensure that the correct ACL's permissions bits are applied:
- d: Delete. Delete a file using the HTTP "Delete" method.
- m: Modify. Put a file in the web space using the HTTP "Put" method.
Please Note: The [server] http-method-disabled-remote entry must not include the PUT or DELETE methods. This entry was introduced in ISAM 7.0.
[{"Product":{"code":"SSPREK","label":"Tivoli Access Manager for e-business"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"WebSEAL","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]
Product Synonym
ISAM TAMeb
Was this topic helpful?
Document Information
More support for:
Tivoli Access Manager for e-business
Software version:
Version Independent
Document number:
484005
Modified date:
16 June 2018
UID
swg21617301
Manage My Notification Subscriptions
