Glenn,
got this in my notes and no point in asking for details since writing json files is unknown to me.
Supported authentication mechanism is: basic; digest; ntlm; token; bearer; urltoken; Outh2
token
the parameters etc appear to be encoded in the token for example see
https://auth0.com/learn/token-based-authentication-made-easy/ in the schema you can have a header block you can specify the %token in there, We actually have 2 types of tokens, header tokens and url tokens
this is a url block from the elasticsearch schema the little token bit is actually defining the token call clusterName so when you see %clusterName is it was actually something defined in the schema. You could define a token to store anything you want and call it anything you want.
{
"src": "",
"xml_ns": "",
"var": "",
"id": "clusterstats",
"url": "/_cluster/stats",
"tokens": {
"clusterName": "$['cluster_name']"
}
},
%token the will hold the value of a token defined in the restmon.cfg
so you create a token at the volumes level that stores the volume name and maybe we call it volumeName
------------------------------
Support Engineer
Broadcom
------------------------------
Original Message:
Sent: 12-09-2020 10:46 AM
From: Glenn Weavind
Subject: Re: Is it possible with UIM to monitor a non CA product trough API which has double Authentication security?
Hi Rich: How does the configuring JSON for the RESTmon schema show the service-account userID and key (of the key/pair), please?
I've not been able to find a document that lists the various authentication options that the probe support, and most of the supplied examples use either no auth, basic or digest.
Thanks.
Original Message:
Sent: 04-15-2019 08:39 AM
From: Rich LANKESTER
Subject: Re: Is it possible with UIM to monitor a non CA product trough API which has double Authentication security?
In our experience with RESTmon in these type of scenarios, we invariably are able to leverage a service account/mode so that normal MFA is not used.