AIOps

All,
I have installed the latest version of the Message Bus Probe and am trying to get it to connect to Nokia NSP version 19.11 (which is supported according to the reference guid here https://www.ibm.com/docs/en/SSSHTQ/messbuspr_nsp-pdf.pdf). I have configured all of the .props, .properties and .json files as directed in the documentation, and am having PARTIAL success. Specifically, the probe is able to authenticate to the Nokia NSP server and I can see the JSON response that includes the access_token which is required for all of the REST API calls after authentication.

The problem is when the probe tries to create a subscription using an HTTP POST to https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions. The problem I see in the log file is the server is returning an HTTP 401 (Unauthorized) error and I see "Invalid username and password" in the log file. This makes me think that the probe is not sending the correct value in the Authorization header. Unfortunately, the logfile redacts the value set in the Authorization header (it actually states "Authorization: <Redacted>" so I can't see what's being passed. So I tried editing the nokaNspRestMultiChannelHttpTransport.json file to add a new header and set its value to "++access_token++" (this is how the dynamic tokens are referenced in the file). I also added "++access_token++" to the end of the subscriptions URI. The goal here was to see if the probe debug output would contain the expanded value of this token. Unfortunately, all I see in the debug output is the string "++access_token++" in both places where I tried to use it. It *seems like* it should expand this into an actual value, so I tested with another token: "++Username++". When I used this token, I could actually see the expanded value in the log file. I also tried with "++refresh_token++", and it acted the same way as "++access+token++".

With the above testing, it looks to me like the probe isn't correctly expanding these tokens. 

Using curl with the correct values (using this page for authentication details and this page for subscriptions details) I can successfully access the URL https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions, and I can see that a new subscription is created. I can also recreate the error seen in the probe log file if I change any character in the access_token when I use it to access the subscriptions URL.

Has anyone gotten this integration to work? Or does anyone have insight into how to get it working?

Thanks,
Frank

------------------------------
Frank Tate
Gulfsoft Consulting
------------------------------

I ran another test, and I now fully believe that the probe has a bug in it. The test I ran was:

ran the curl command to access the REST API and get an access_toekn value (these are valid for an hour by default)
I then hard-coded that value into the Authentication header of the subscription API call
THIS WORKED to successfully create a subscription

Based on the above, I can tell that the probe is not doing what it's supposed to.
I'm hoping someone from IBM with in-depth knowledge of the probe can comment.

------------------------------
Frank Tate
Gulfsoft Consulting
------------------------------

Original Message:
Sent: Tue October 05, 2021 04:15 PM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

All,
I have installed the latest version of the Message Bus Probe and am trying to get it to connect to Nokia NSP version 19.11 (which is supported according to the reference guid here https://www.ibm.com/docs/en/SSSHTQ/messbuspr_nsp-pdf.pdf). I have configured all of the .props, .properties and .json files as directed in the documentation, and am having PARTIAL success. Specifically, the probe is able to authenticate to the Nokia NSP server and I can see the JSON response that includes the access_token which is required for all of the REST API calls after authentication.

The problem is when the probe tries to create a subscription using an HTTP POST to https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions. The problem I see in the log file is the server is returning an HTTP 401 (Unauthorized) error and I see "Invalid username and password" in the log file. This makes me think that the probe is not sending the correct value in the Authorization header. Unfortunately, the logfile redacts the value set in the Authorization header (it actually states "Authorization: <Redacted>" so I can't see what's being passed. So I tried editing the nokaNspRestMultiChannelHttpTransport.json file to add a new header and set its value to "++access_token++" (this is how the dynamic tokens are referenced in the file). I also added "++access_token++" to the end of the subscriptions URI. The goal here was to see if the probe debug output would contain the expanded value of this token. Unfortunately, all I see in the debug output is the string "++access_token++" in both places where I tried to use it. It *seems like* it should expand this into an actual value, so I tested with another token: "++Username++". When I used this token, I could actually see the expanded value in the log file. I also tried with "++refresh_token++", and it acted the same way as "++access+token++".

With the above testing, it looks to me like the probe isn't correctly expanding these tokens. 

Using curl with the correct values (using this page for authentication details and this page for subscriptions details) I can successfully access the URL https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions, and I can see that a new subscription is created. I can also recreate the error seen in the probe log file if I change any character in the access_token when I use it to access the subscriptions URL.

Has anyone gotten this integration to work? Or does anyone have insight into how to get it working?

Thanks,
Frank

------------------------------
Frank Tate
Gulfsoft Consulting
------------------------------

Hi Frank,

please open a Case with our support in parallel:

https://www.ibm.com/mysupport/CommunitiesLogin?startURL=/s/createrecord/NewCase
so we have this in the records too. Meanwhile I will ask around if this is a know "feature".

Kind regards,

Fred

------------------------------
Fred Klein
Client Technical Manager - Analytics
Hybrid Cloud Management SWAT Team Lead
Executive IT-Specialist
IBM Automation
https://ibm.biz/swat_explains
------------------------------

Original Message:
Sent: Tue October 05, 2021 04:31 PM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

I ran another test, and I now fully believe that the probe has a bug in it. The test I ran was:

ran the curl command to access the REST API and get an access_toekn value (these are valid for an hour by default)
I then hard-coded that value into the Authentication header of the subscription API call
THIS WORKED to successfully create a subscription

Based on the above, I can tell that the probe is not doing what it's supposed to.
I'm hoping someone from IBM with in-depth knowledge of the probe can comment.

------------------------------
Frank Tate
Gulfsoft Consulting

Original Message:
Sent: Tue October 05, 2021 04:15 PM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

All,
I have installed the latest version of the Message Bus Probe and am trying to get it to connect to Nokia NSP version 19.11 (which is supported according to the reference guid here https://www.ibm.com/docs/en/SSSHTQ/messbuspr_nsp-pdf.pdf). I have configured all of the .props, .properties and .json files as directed in the documentation, and am having PARTIAL success. Specifically, the probe is able to authenticate to the Nokia NSP server and I can see the JSON response that includes the access_token which is required for all of the REST API calls after authentication.

The problem is when the probe tries to create a subscription using an HTTP POST to https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions. The problem I see in the log file is the server is returning an HTTP 401 (Unauthorized) error and I see "Invalid username and password" in the log file. This makes me think that the probe is not sending the correct value in the Authorization header. Unfortunately, the logfile redacts the value set in the Authorization header (it actually states "Authorization: <Redacted>" so I can't see what's being passed. So I tried editing the nokaNspRestMultiChannelHttpTransport.json file to add a new header and set its value to "++access_token++" (this is how the dynamic tokens are referenced in the file). I also added "++access_token++" to the end of the subscriptions URI. The goal here was to see if the probe debug output would contain the expanded value of this token. Unfortunately, all I see in the debug output is the string "++access_token++" in both places where I tried to use it. It *seems like* it should expand this into an actual value, so I tested with another token: "++Username++". When I used this token, I could actually see the expanded value in the log file. I also tried with "++refresh_token++", and it acted the same way as "++access+token++".

With the above testing, it looks to me like the probe isn't correctly expanding these tokens. 

Using curl with the correct values (using this page for authentication details and this page for subscriptions details) I can successfully access the URL https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions, and I can see that a new subscription is created. I can also recreate the error seen in the probe log file if I change any character in the access_token when I use it to access the subscriptions URL.

Has anyone gotten this integration to work? Or does anyone have insight into how to get it working?

Thanks,
Frank

------------------------------
Frank Tate
Gulfsoft Consulting
------------------------------

Thanks for looking into it, Fred.

The link you provided doesn't currently work. I get an HTTP 503 (Service Unavailable) error. However, I did open PMR 48698,756,000 through PartnerWorld.

Frank

------------------------------
Frank Tate
Gulfsoft Consulting
------------------------------

Original Message:
Sent: Wed October 06, 2021 02:57 AM
From: Fred Harald Klein
Subject: Unable to get Message Bus Probe for Nokia NSP working

Hi Frank,

please open a Case with our support in parallel:

https://www.ibm.com/mysupport/CommunitiesLogin?startURL=/s/createrecord/NewCase
so we have this in the records too. Meanwhile I will ask around if this is a know "feature".

Kind regards,

Fred

------------------------------
Fred Klein
Client Technical Manager - Analytics
Hybrid Cloud Management SWAT Team Lead
Executive IT-Specialist
IBM Automation
https://ibm.biz/swat_explains

Original Message:
Sent: Tue October 05, 2021 04:31 PM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

I ran another test, and I now fully believe that the probe has a bug in it. The test I ran was:

ran the curl command to access the REST API and get an access_toekn value (these are valid for an hour by default)
I then hard-coded that value into the Authentication header of the subscription API call
THIS WORKED to successfully create a subscription

Based on the above, I can tell that the probe is not doing what it's supposed to.
I'm hoping someone from IBM with in-depth knowledge of the probe can comment.

------------------------------
Frank Tate
Gulfsoft Consulting

Original Message:
Sent: Tue October 05, 2021 04:15 PM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

All,
I have installed the latest version of the Message Bus Probe and am trying to get it to connect to Nokia NSP version 19.11 (which is supported according to the reference guid here https://www.ibm.com/docs/en/SSSHTQ/messbuspr_nsp-pdf.pdf). I have configured all of the .props, .properties and .json files as directed in the documentation, and am having PARTIAL success. Specifically, the probe is able to authenticate to the Nokia NSP server and I can see the JSON response that includes the access_token which is required for all of the REST API calls after authentication.

The problem is when the probe tries to create a subscription using an HTTP POST to https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions. The problem I see in the log file is the server is returning an HTTP 401 (Unauthorized) error and I see "Invalid username and password" in the log file. This makes me think that the probe is not sending the correct value in the Authorization header. Unfortunately, the logfile redacts the value set in the Authorization header (it actually states "Authorization: <Redacted>" so I can't see what's being passed. So I tried editing the nokaNspRestMultiChannelHttpTransport.json file to add a new header and set its value to "++access_token++" (this is how the dynamic tokens are referenced in the file). I also added "++access_token++" to the end of the subscriptions URI. The goal here was to see if the probe debug output would contain the expanded value of this token. Unfortunately, all I see in the debug output is the string "++access_token++" in both places where I tried to use it. It *seems like* it should expand this into an actual value, so I tested with another token: "++Username++". When I used this token, I could actually see the expanded value in the log file. I also tried with "++refresh_token++", and it acted the same way as "++access+token++".

With the above testing, it looks to me like the probe isn't correctly expanding these tokens. 

Using curl with the correct values (using this page for authentication details and this page for subscriptions details) I can successfully access the URL https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions, and I can see that a new subscription is created. I can also recreate the error seen in the probe log file if I change any character in the access_token when I use it to access the subscriptions URL.

Has anyone gotten this integration to work? Or does anyone have insight into how to get it working?

Thanks,
Frank

------------------------------
Frank Tate
Gulfsoft Consulting
------------------------------

I just configured a simple HTTPS server in python using the code here: https://gist.github.com/karlp/3987911 and modified it to log all headers using some of the logging.error() call I found here: https://gist.github.com/phrawzty/62540f146ee5e74ea1ab. I then created/copied the appropriate keys and certs to the appropriate keystore.
I then changed the subscription URL to be https://localhost:443/... and when I ran the probe, I can see that it is passing "Bearer ++access_token++" as the value of the Authorization header, so I know for certain that it is not expanding that token to the correct value. So this is definitely a bug.

------------------------------
Frank Tate
Gulfsoft Consulting
------------------------------

Original Message:
Sent: Wed October 06, 2021 02:57 AM
From: Fred Harald Klein
Subject: Unable to get Message Bus Probe for Nokia NSP working

Hi Frank,

please open a Case with our support in parallel:

https://www.ibm.com/mysupport/CommunitiesLogin?startURL=/s/createrecord/NewCase
so we have this in the records too. Meanwhile I will ask around if this is a know "feature".

Kind regards,

Fred

------------------------------
Fred Klein
Client Technical Manager - Analytics
Hybrid Cloud Management SWAT Team Lead
Executive IT-Specialist
IBM Automation
https://ibm.biz/swat_explains

Original Message:
Sent: Tue October 05, 2021 04:31 PM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

I ran another test, and I now fully believe that the probe has a bug in it. The test I ran was:

ran the curl command to access the REST API and get an access_toekn value (these are valid for an hour by default)
I then hard-coded that value into the Authentication header of the subscription API call
THIS WORKED to successfully create a subscription

Based on the above, I can tell that the probe is not doing what it's supposed to.
I'm hoping someone from IBM with in-depth knowledge of the probe can comment.

------------------------------
Frank Tate
Gulfsoft Consulting

Original Message:
Sent: Tue October 05, 2021 04:15 PM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

All,
I have installed the latest version of the Message Bus Probe and am trying to get it to connect to Nokia NSP version 19.11 (which is supported according to the reference guid here https://www.ibm.com/docs/en/SSSHTQ/messbuspr_nsp-pdf.pdf). I have configured all of the .props, .properties and .json files as directed in the documentation, and am having PARTIAL success. Specifically, the probe is able to authenticate to the Nokia NSP server and I can see the JSON response that includes the access_token which is required for all of the REST API calls after authentication.

The problem is when the probe tries to create a subscription using an HTTP POST to https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions. The problem I see in the log file is the server is returning an HTTP 401 (Unauthorized) error and I see "Invalid username and password" in the log file. This makes me think that the probe is not sending the correct value in the Authorization header. Unfortunately, the logfile redacts the value set in the Authorization header (it actually states "Authorization: <Redacted>" so I can't see what's being passed. So I tried editing the nokaNspRestMultiChannelHttpTransport.json file to add a new header and set its value to "++access_token++" (this is how the dynamic tokens are referenced in the file). I also added "++access_token++" to the end of the subscriptions URI. The goal here was to see if the probe debug output would contain the expanded value of this token. Unfortunately, all I see in the debug output is the string "++access_token++" in both places where I tried to use it. It *seems like* it should expand this into an actual value, so I tested with another token: "++Username++". When I used this token, I could actually see the expanded value in the log file. I also tried with "++refresh_token++", and it acted the same way as "++access+token++".

With the above testing, it looks to me like the probe isn't correctly expanding these tokens. 

Using curl with the correct values (using this page for authentication details and this page for subscriptions details) I can successfully access the URL https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions, and I can see that a new subscription is created. I can also recreate the error seen in the probe log file if I change any character in the access_token when I use it to access the subscriptions URL.

Has anyone gotten this integration to work? Or does anyone have insight into how to get it working?

Thanks,
Frank

------------------------------
Frank Tate
Gulfsoft Consulting
------------------------------

Original Message:
Sent: 10/6/2021 10:40:00 AM
From: Frank Tate
Subject: RE: Unable to get Message Bus Probe for Nokia NSP working

I just configured a simple HTTPS server in python using the code here: https://gist.github.com/karlp/3987911 and modified it to log all headers using some of the logging.error() call I found here: https://gist.github.com/phrawzty/62540f146ee5e74ea1ab. I then created/copied the appropriate keys and certs to the appropriate keystore.
I then changed the subscription URL to be https://localhost:443/... and when I ran the probe, I can see that it is passing "Bearer ++access_token++" as the value of the Authorization header, so I know for certain that it is not expanding that token to the correct value. So this is definitely a bug.

------------------------------
Frank Tate
Gulfsoft Consulting
------------------------------

Original Message:
Sent: Wed October 06, 2021 02:57 AM
From: Fred Harald Klein
Subject: Unable to get Message Bus Probe for Nokia NSP working

Hi Frank,

please open a Case with our support in parallel:

https://www.ibm.com/mysupport/CommunitiesLogin?startURL=/s/createrecord/NewCase
so we have this in the records too. Meanwhile I will ask around if this is a know "feature".

Kind regards,

Fred

------------------------------
Fred Klein
Client Technical Manager - Analytics
Hybrid Cloud Management SWAT Team Lead
Executive IT-Specialist
IBM Automation
https://ibm.biz/swat_explains

Original Message:
Sent: Tue October 05, 2021 04:31 PM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

I ran another test, and I now fully believe that the probe has a bug in it. The test I ran was:

ran the curl command to access the REST API and get an access_toekn value (these are valid for an hour by default)
I then hard-coded that value into the Authentication header of the subscription API call
THIS WORKED to successfully create a subscription

Based on the above, I can tell that the probe is not doing what it's supposed to.
I'm hoping someone from IBM with in-depth knowledge of the probe can comment.

------------------------------
Frank Tate
Gulfsoft Consulting

Original Message:
Sent: Tue October 05, 2021 04:15 PM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

All,
I have installed the latest version of the Message Bus Probe and am trying to get it to connect to Nokia NSP version 19.11 (which is supported according to the reference guid here https://www.ibm.com/docs/en/SSSHTQ/messbuspr_nsp-pdf.pdf). I have configured all of the .props, .properties and .json files as directed in the documentation, and am having PARTIAL success. Specifically, the probe is able to authenticate to the Nokia NSP server and I can see the JSON response that includes the access_token which is required for all of the REST API calls after authentication.

The problem is when the probe tries to create a subscription using an HTTP POST to https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions. The problem I see in the log file is the server is returning an HTTP 401 (Unauthorized) error and I see "Invalid username and password" in the log file. This makes me think that the probe is not sending the correct value in the Authorization header. Unfortunately, the logfile redacts the value set in the Authorization header (it actually states "Authorization: <Redacted>" so I can't see what's being passed. So I tried editing the nokaNspRestMultiChannelHttpTransport.json file to add a new header and set its value to "++access_token++" (this is how the dynamic tokens are referenced in the file). I also added "++access_token++" to the end of the subscriptions URI. The goal here was to see if the probe debug output would contain the expanded value of this token. Unfortunately, all I see in the debug output is the string "++access_token++" in both places where I tried to use it. It *seems like* it should expand this into an actual value, so I tested with another token: "++Username++". When I used this token, I could actually see the expanded value in the log file. I also tried with "++refresh_token++", and it acted the same way as "++access+token++".

With the above testing, it looks to me like the probe isn't correctly expanding these tokens. 

Using curl with the correct values (using this page for authentication details and this page for subscriptions details) I can successfully access the URL https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions, and I can see that a new subscription is created. I can also recreate the error seen in the probe log file if I change any character in the access_token when I use it to access the subscriptions URL.

Has anyone gotten this integration to work? Or does anyone have insight into how to get it working?

Thanks,
Frank

------------------------------
Frank Tate
Gulfsoft Consulting
------------------------------

Great, finally.

God job Frank.

------------------------------
Fred Klein
Client Technical Manager - Analytics
Hybrid Cloud Management SWAT Team Lead
Executive IT-Specialist
IBM Automation
https://ibm.biz/swat_explains
------------------------------

Original Message:
Sent: Sun October 24, 2021 11:22 AM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

Problem solved by installing version 17 of the Message Bus probe (released on 9/30, apparently).

Frank

Frank Tate
MBA, PMP, CISSP
CEO, Gulfsoft Consulting
Frank.Tate@gulfsoft.com
http://www.gulfsoft.com
ph: 304-376-6183

Original Message:
Sent: 10/6/2021 10:40:00 AM
From: Frank Tate
Subject: RE: Unable to get Message Bus Probe for Nokia NSP working

I just configured a simple HTTPS server in python using the code here: https://gist.github.com/karlp/3987911 and modified it to log all headers using some of the logging.error() call I found here: https://gist.github.com/phrawzty/62540f146ee5e74ea1ab. I then created/copied the appropriate keys and certs to the appropriate keystore.
I then changed the subscription URL to be https://localhost:443/... and when I ran the probe, I can see that it is passing "Bearer ++access_token++" as the value of the Authorization header, so I know for certain that it is not expanding that token to the correct value. So this is definitely a bug.

------------------------------
Frank Tate
Gulfsoft Consulting

Original Message:
Sent: Wed October 06, 2021 02:57 AM
From: Fred Harald Klein
Subject: Unable to get Message Bus Probe for Nokia NSP working

Hi Frank,

please open a Case with our support in parallel:

https://www.ibm.com/mysupport/CommunitiesLogin?startURL=/s/createrecord/NewCase
so we have this in the records too. Meanwhile I will ask around if this is a know "feature".

Kind regards,

Fred

------------------------------
Fred Klein
Client Technical Manager - Analytics
Hybrid Cloud Management SWAT Team Lead
Executive IT-Specialist
IBM Automation
https://ibm.biz/swat_explains

Original Message:
Sent: Tue October 05, 2021 04:31 PM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

I ran another test, and I now fully believe that the probe has a bug in it. The test I ran was:

ran the curl command to access the REST API and get an access_toekn value (these are valid for an hour by default)
I then hard-coded that value into the Authentication header of the subscription API call
THIS WORKED to successfully create a subscription

Based on the above, I can tell that the probe is not doing what it's supposed to.
I'm hoping someone from IBM with in-depth knowledge of the probe can comment.

------------------------------
Frank Tate
Gulfsoft Consulting

Original Message:
Sent: Tue October 05, 2021 04:15 PM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

All,
I have installed the latest version of the Message Bus Probe and am trying to get it to connect to Nokia NSP version 19.11 (which is supported according to the reference guid here https://www.ibm.com/docs/en/SSSHTQ/messbuspr_nsp-pdf.pdf). I have configured all of the .props, .properties and .json files as directed in the documentation, and am having PARTIAL success. Specifically, the probe is able to authenticate to the Nokia NSP server and I can see the JSON response that includes the access_token which is required for all of the REST API calls after authentication.

The problem is when the probe tries to create a subscription using an HTTP POST to https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions. The problem I see in the log file is the server is returning an HTTP 401 (Unauthorized) error and I see "Invalid username and password" in the log file. This makes me think that the probe is not sending the correct value in the Authorization header. Unfortunately, the logfile redacts the value set in the Authorization header (it actually states "Authorization: <Redacted>" so I can't see what's being passed. So I tried editing the nokaNspRestMultiChannelHttpTransport.json file to add a new header and set its value to "++access_token++" (this is how the dynamic tokens are referenced in the file). I also added "++access_token++" to the end of the subscriptions URI. The goal here was to see if the probe debug output would contain the expanded value of this token. Unfortunately, all I see in the debug output is the string "++access_token++" in both places where I tried to use it. It *seems like* it should expand this into an actual value, so I tested with another token: "++Username++". When I used this token, I could actually see the expanded value in the log file. I also tried with "++refresh_token++", and it acted the same way as "++access+token++".

With the above testing, it looks to me like the probe isn't correctly expanding these tokens. 

Using curl with the correct values (using this page for authentication details and this page for subscriptions details) I can successfully access the URL https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions, and I can see that a new subscription is created. I can also recreate the error seen in the probe log file if I change any character in the access_token when I use it to access the subscriptions URL.

Has anyone gotten this integration to work? Or does anyone have insight into how to get it working?

Thanks,
Frank

------------------------------
Frank Tate
Gulfsoft Consulting
------------------------------

Hi Frank and Fred,

I had a similar issue last week but I was using that version 17 already.

I my case the issue was related to use of SSL in props file and I had to run the probe with Java 11. Another difference in my scenario was that the NSP was at version 21.

Best Regards,

------------------------------
Rudson Ramos
------------------------------

Original Message:
Sent: Mon October 25, 2021 03:32 AM
From: Fred Harald Klein
Subject: Unable to get Message Bus Probe for Nokia NSP working

Great, finally.

God job Frank.

------------------------------
Fred Klein
Client Technical Manager - Analytics
Hybrid Cloud Management SWAT Team Lead
Executive IT-Specialist
IBM Automation
https://ibm.biz/swat_explains

Original Message:
Sent: Sun October 24, 2021 11:22 AM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

Problem solved by installing version 17 of the Message Bus probe (released on 9/30, apparently).

Frank

Frank Tate
MBA, PMP, CISSP
CEO, Gulfsoft Consulting
Frank.Tate@gulfsoft.com
http://www.gulfsoft.com
ph: 304-376-6183

Original Message:
Sent: 10/6/2021 10:40:00 AM
From: Frank Tate
Subject: RE: Unable to get Message Bus Probe for Nokia NSP working

I just configured a simple HTTPS server in python using the code here: https://gist.github.com/karlp/3987911 and modified it to log all headers using some of the logging.error() call I found here: https://gist.github.com/phrawzty/62540f146ee5e74ea1ab. I then created/copied the appropriate keys and certs to the appropriate keystore.
I then changed the subscription URL to be https://localhost:443/... and when I ran the probe, I can see that it is passing "Bearer ++access_token++" as the value of the Authorization header, so I know for certain that it is not expanding that token to the correct value. So this is definitely a bug.

------------------------------
Frank Tate
Gulfsoft Consulting

Original Message:
Sent: Wed October 06, 2021 02:57 AM
From: Fred Harald Klein
Subject: Unable to get Message Bus Probe for Nokia NSP working

Hi Frank,

please open a Case with our support in parallel:

https://www.ibm.com/mysupport/CommunitiesLogin?startURL=/s/createrecord/NewCase
so we have this in the records too. Meanwhile I will ask around if this is a know "feature".

Kind regards,

Fred

------------------------------
Fred Klein
Client Technical Manager - Analytics
Hybrid Cloud Management SWAT Team Lead
Executive IT-Specialist
IBM Automation
https://ibm.biz/swat_explains

Original Message:
Sent: Tue October 05, 2021 04:31 PM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

I ran another test, and I now fully believe that the probe has a bug in it. The test I ran was:

ran the curl command to access the REST API and get an access_toekn value (these are valid for an hour by default)
I then hard-coded that value into the Authentication header of the subscription API call
THIS WORKED to successfully create a subscription

Based on the above, I can tell that the probe is not doing what it's supposed to.
I'm hoping someone from IBM with in-depth knowledge of the probe can comment.

------------------------------
Frank Tate
Gulfsoft Consulting

Original Message:
Sent: Tue October 05, 2021 04:15 PM
From: Frank Tate
Subject: Unable to get Message Bus Probe for Nokia NSP working

All,
I have installed the latest version of the Message Bus Probe and am trying to get it to connect to Nokia NSP version 19.11 (which is supported according to the reference guid here https://www.ibm.com/docs/en/SSSHTQ/messbuspr_nsp-pdf.pdf). I have configured all of the .props, .properties and .json files as directed in the documentation, and am having PARTIAL success. Specifically, the probe is able to authenticate to the Nokia NSP server and I can see the JSON response that includes the access_token which is required for all of the REST API calls after authentication.

The problem is when the probe tries to create a subscription using an HTTP POST to https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions. The problem I see in the log file is the server is returning an HTTP 401 (Unauthorized) error and I see "Invalid username and password" in the log file. This makes me think that the probe is not sending the correct value in the Authorization header. Unfortunately, the logfile redacts the value set in the Authorization header (it actually states "Authorization: <Redacted>" so I can't see what's being passed. So I tried editing the nokaNspRestMultiChannelHttpTransport.json file to add a new header and set its value to "++access_token++" (this is how the dynamic tokens are referenced in the file). I also added "++access_token++" to the end of the subscriptions URI. The goal here was to see if the probe debug output would contain the expanded value of this token. Unfortunately, all I see in the debug output is the string "++access_token++" in both places where I tried to use it. It *seems like* it should expand this into an actual value, so I tested with another token: "++Username++". When I used this token, I could actually see the expanded value in the log file. I also tried with "++refresh_token++", and it acted the same way as "++access+token++".

With the above testing, it looks to me like the probe isn't correctly expanding these tokens. 

Using curl with the correct values (using this page for authentication details and this page for subscriptions details) I can successfully access the URL https://{{server}}:8544/nbi-notification/api/v1/notifications/subscriptions, and I can see that a new subscription is created. I can also recreate the error seen in the probe log file if I change any character in the access_token when I use it to access the subscriptions URL.

Has anyone gotten this integration to work? Or does anyone have insight into how to get it working?

Thanks,
Frank

------------------------------
Frank Tate
Gulfsoft Consulting
------------------------------