IBM Security Verify

  • 1.  Quiesceing a wrp instance in a Kubernetes pod

    Posted 7 days ago
    Hi,

    Is there a way to gracefully stop a wrp instance before killing the pod?
    We have made changes to junctions, published the configuration and these changes do not seem to take effect without a wrp container restart.
    Currently the "easy" way to restart is to kill the pod and start a new one which will then read the new configuration file.
    On the other hand, this isn't very polite to those users that already logged in :-)


    Rgds

    ------------------------------
    Anders Domeij
    CGI Sweden AB
    ------------------------------


  • 2.  RE: Quiesceing a wrp instance in a Kubernetes pod

    Posted 7 days ago
    Anders,
     
    Unfortunately there is currently no 'nice' way to tell the WRP container that new junction configuration information is available without having to restart the pod.  If you are concerned about users having to authenticate again the only real option at the moment is to use failover cookies, or configure the WRP to use an external session cache (Redis would be the best option here).
     
    I hope that this helps.
     
     
    Scott A. Exton
    Senior Software Engineer
    Chief Programmer - IBM Security Verify Access
    IBM Master Inventor
     
       
     
     



    Original Message