We are using Skyline’s “Inmarsat BGAN Manager” driver (https://catalog.dataminer.services/result/driver/6295). We have had a message from our supplier saying the following:
We are currently replacing a deprecated authentication middleware in RTM with a modern one. This change may have impact on the way the RTM API handles requests. My aim is to be as backwards compatible as possible so that existing applications such as your DataMiner won’t break.
Would you or your developers be able to send us some info on how your data miner currently authenticates with the API? I am guessing it’s using the “ArqivaApp” client id and some scope value (most likely “api1”) as well as a dedicated API user account in RTM. Would be very helpful if your development team can share some logic or even better some sample CURL commands that I can use to test against the new middle ware.
Could Skyline (or anyone in the community) possibly help by providing us this information please?
Hi Alex,
The Inmarsat BGAN Manager uses a REST API get method described in the ‘RTM REST API getting Started – c#’ API documentation. I have forwarded the documentation across in a separate email.
A sample of the commands which are built into our protocol are below:
There is an example on how the requests looks when using both snippets combined.
What will help most here is if I can communicate with Nigel Scrivin and retrieve a Wireshark capture of the communications between DataMiner and the RTM module in your environment, then we can forward this across to the vendor for confirmation on the backwards compatibility.
NOTE: The authentication is a two step process, request for token via credentials then use of the token for future queries for validation.