IBM Verify

IBM Verify

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

 View Only

  • 1.  HTTP PATCH

    Posted Thu June 16, 2022 10:19 AM
    Hi all,

    is there a configuration to allow the use of the HTTP PATCH method? It's supported by the ISVA proxies? The HTTP response now it 501

    Thank you,
    Natascia

    ------------------------------
    Natascia Roia
    ------------------------------


  • 2.  RE: HTTP PATCH

    Posted Thu June 16, 2022 03:56 PM

    Natascia,

     

    WebSEAL is able to forward the PATCH request onto junctioned servers, but does not support the PATCH method when accessing a local junction.

     

    The 'http-method-disabled-remote' configuration entry within the '[server]' stanza lists the methods for which WebSEAL will return a 501.  I suspect that you might have the 'PATCH' method listed here, and if so, it should be removed.

     

    If you are still getting a 501 after updating the 'http-method-disabled-remote' configuration entry I would then suggest that you enable to pdweb.snoop tracing to check that the 501 is not coming from the junctioned server.

     

    I hope that this helps.

     

     

    Scott A. Exton
    Senior Software Engineer
    Chief Programmer - IBM Security Verify Access
    IBM Master Inventor

    cid4122760825*<a href=image002.png@01D85F83.85516C50">

     

     

     




    Original Message


  • 3.  RE: HTTP PATCH

    Posted Fri June 17, 2022 09:08 AM
    Edited by Jon Harry Fri June 17, 2022 09:11 AM
    Hi Natascia,

    It's also worth noting that, by default, the "r" (read) permission in ACL allows PATCH operation.  If you want to independently control use of PATCH, you can assign it to a different permission bit in the Reverse Proxy configuration.

    Jon.

    ------------------------------
    IAM Jon
    ------------------------------

    Original Message