AIOps

Expand all | Collapse all

LogDNA - NOI Integration fails with 403 Not Authenticated Error

  • 1.  LogDNA - NOI Integration fails with 403 Not Authenticated Error

    Posted Wed September 08, 2021 09:43 AM

    I'm trying to integrate my LogDNA views with Netcool Omnibus for alerting application errors seen in the logs. 

    When I test the integration with NOI, I get the message: "Authenticaion error: Not authenticated - no credentials" even though I passed the authorization as a header as well as in the URL itself (https://username:password@NOI-URL:port). This does not work in the NOI instance that have certificates applied for authentication. 

    Has anyone observed this behaviour from LogDNA? 

    PS: The same method of authentication works for other tools like Instana etc. 


    Best Regards,

    Pavan



    ------------------------------
    Pavana Kumar N
    ------------------------------


  • 2.  RE: LogDNA - NOI Integration fails with 403 Not Authenticated Error

    Posted Mon September 13, 2021 06:45 AM
    Not sure if you are still stuck. If yes, please share relevant logs for the community to assist you.

    Thanks, Veer

    ------------------------------
    Veeramani Nambi
    Offering Manager, GoToMarket - Communities
    ------------------------------



  • 3.  RE: LogDNA - NOI Integration fails with 403 Not Authenticated Error

    Posted Mon September 13, 2021 07:20 AM
    Edited by mario schuerewegen Mon September 13, 2021 07:21 AM

    you are missing some very basic information here..

    so you are trying to send webhook based messages from logDNA to NOI.

    but to which component of NOI?   A probe?  a webhook integration (UI), aiops.aimanager ?

    reason i ask is.  the UI based webhook integration does not have authentication afaik.

    https://www.ibm.com/docs/en/noi/1.6.3?topic=SSTPTP_1.6.3/com.ibm.netcool_ops.doc/cem/em_definingsources.html

    the probe based solution has more configurable options

    https://www.ibm.com/docs/en/noi/1.6.3?topic=SSTPTP_1.6.3/com.ibm.netcool_ops.doc/cem/em_definingsources.html



    ------------------------------
    mario schuerewegen
    IBM
    Brussels

    ------------------------------



  • 4.  RE: LogDNA - NOI Integration fails with 403 Not Authenticated Error

    Posted Mon September 13, 2021 07:40 AM

    Hey Mario,

    We are sending it to a message bus probe. Also, to note, when we disable the authorization from Netcool end, we are able to receive the payload. 
    What am I missing here? 

    Best Regards,

    Pavan



    ------------------------------
    Pavana Kumar N
    ------------------------------



  • 5.  RE: LogDNA - NOI Integration fails with 403 Not Authenticated Error

    Posted Mon September 13, 2021 07:03 AM
      |   view attached

    Hello Veeramani,

    Thank you for the response. Yes we are still facing the issue. 

    I'm try to send the alerts to the Netcool Omnibus that requires authorization, I tried passing them both as headers and along with the Netcool URL.
    I'm attaching a screenshot of what my Webhook payload looks like.

    Below is the log in my Netcool when the payload / alert is received:

    2021-09-13T02:56:32: Debug: D-JPR-000-000: HttpRequestHandler]: Connection from client 'c.e7.e443.ip4.static.sl-reverse.com' (46111) to server port 'https:9090'.
    2021-09-13T02:56:32: Debug: D-JPR-000-000: [HttpParser]: Successfully read HTTP header.
    2021-09-13T02:56:32: Debug: D-JPR-000-000: [HttpParser]: Reading payload size = 49
    2021-09-13T02:56:32: Debug: D-JPR-000-000: [HttpParser]: Successfully read HTTP payload.
    2021-09-13T02:56:32: Debug: D-JPR-000-000: [HttpRequestHandler]: Authenticaion error: Not authenticated - no credentials
    2021-09-13T02:56:32: Debug: D-JPR-000-000: [HttpRequestHandler]: Sent response [403]
    2021-09-13T02:56:32: Debug


    Best Regards,

    Pavan



    ------------------------------
    Pavana Kumar N
    ------------------------------



  • 6.  RE: LogDNA - NOI Integration fails with 403 Not Authenticated Error

    Posted Mon September 13, 2021 07:52 AM
    Edited by mario schuerewegen Mon September 13, 2021 07:53 AM

    that sounds like a proper support case.  not just something to easily answer on a forum

    did you check Jim's troubleshooting docs ?

    https://www.ibm.com/support/pages/system/files/inline-files/$FILE/XML_MessagebusIntegration_SupportsGuide_44.pdf


    look at page 27   HTTP BasicAuth example

    ------------------------------
    mario schuerewegen
    IBM
    Brussels
    ------------------------------