IBM Security Verify

 View Only
  • 1.  How to configure request.log on stdout?

    Posted Fri December 04, 2020 07:03 AM
    Hi to all,
    I want to configure request.log on stdout because I can see its on ELK Dashboard.
    I modified this parameters in WebSEAL configuration file:
    [logging]
    # Enable the request log
    requests = yes

    # Enable the the referer log
    #referers = no
    referers = yes

    # Enable the user agent log
    #agents = no
    agents = yes

    and added this lines under

    #----------------------
    # AUTHORIZATION API LOGGING
    #----------------------

    logcfg = http.clf:stdout path=request.log,flush=20,rollover_size=900000000,max_rollover_files=20,log_id=http,buffer_size=8192,queue_size=48
    logcfg = http.ref:stdout path=request.log,flush=20,rollover_size=900000000,max_rollover_files=20,log_id=http,buffer_size=8192,queue_size=48
    logcfg = http.agent:stdout path=request.log,flush=20,rollover_size=900000000,max_rollover_files=20,log_id=http,buffer_size=8192,queue_size=48
    logcfg = http.clf:stderr path=request.log,flush=20,rollover_size=900000000,max_rollover_files=20,log_id=http,buffer_size=8192,queue_size=48
    logcfg = http.ref:stderr path=request.log,flush=20,rollover_size=900000000,max_rollover_files=20,log_id=http,buffer_size=8192,queue_size=48
    logcfg = http.agent:stderr path=request.log,flush=20,rollover_size=900000000,max_rollover_files=20,log_id=http,buffer_size=8192,queue_size=48

    but on the Dashboard I can see only error like these:
    wga_notifications: WGAWA0045W:: WGA_events::
    or 
    mesa_control[2676]: Policy changes committed

    Do I missed some configurations?
    Have I other to do?

    Thanks for your help,
    Claudio


    ------------------------------
    Claudio Laganà
    ------------------------------


  • 2.  RE: How to configure request.log on stdout?

    Posted Mon March 01, 2021 03:40 AM
    Hi,
    just to inform you, but it seems that ISAM version 9.0.5 does not have this possibility.

    ------------------------------
    Claudio Laganà
    ------------------------------



  • 3.  RE: How to configure request.log on stdout?

    Posted Mon March 01, 2021 01:09 PM

    Hey there, is it correct ? the ISAM does not support it?

    Thx.

    Empresa de TI OneIT



    ------------------------------
    Leonardo Lopes OneIT
    ------------------------------



  • 4.  RE: How to configure request.log on stdout?

    Posted Mon March 01, 2021 03:36 PM
    Claudio,
     
    Unfortunately the 'logcfg' configuration entries are not going to help in this instance because the request/referer/agent logs use a different configuration mechanism.  At the moment there is no way to be able to configure the referer and agent logs to be sent to stdout.  If you are using a 10.0 or 10.0.1 build you can however send the request log to stdout by changing the requests-file configuration entry to 'stdout'.
     
    I hope that this helps.
     
     

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

    IBM Master Inventor

     
     





  • 5.  RE: How to configure request.log on stdout?

    Posted Tue March 02, 2021 03:55 AM
    Hi Scott,
    running tests, from version 9.0.7 IF5, with this type of configuration:

    [logging]
    server-log-cfg = file path=msg__webseald-default.log,hi_water=1,flush_interval=20,rollover_size=90000000,max_rollover_files=20

    [aznapi-configuration]
    logcfg = http.clf:stdout hi_water=1,flush_interval=1,queue_size=50
    logcfg = http.clf:file path=request.log,flush=10,rollover=1000000,max_rollover_files=10,log=request,buffer_size=8192,queue_size=48,log_id=request

    You can see the request.log both in the local file and in the stdout log (I tested it in the Docker version).

    Hope this will be useful to you.

    Best regards,
    Claudio

    ------------------------------
    Claudio Laganà
    ------------------------------