entityID in JSON metrics?

[Cantor, Scott]

On 12/16/16, 4:52 PM, "users on behalf of Paul Caskey" <users-bounces at shibboleth.net on behalf of pcaskey at internet2.edu> wrote:

>    Is there a way I’m not seeing to get the IdP’s entityID (idp.entityID) output in the JSON data when retrieving metrics
> from the new Metrics REST API (which is very nice, BTW)?

No, but that's basically because there isn't one entityID. The entityID is a setting on the RelyingPartyConfiguration, so it's dependent on who asks. There's the default of course but no inherent requirement that the default setting ever gets used, so it's problematic to think of that way.
     
>    It would sure help to have that when attempting to process data from multiple IdPs (especially when using http
> reporting).

I think it would be more appropriate to come at this from the point of view of a dedicated identifier that is obviously going to *be* the entityID in 99.9% of cases, but is formally speaking something specific to the problem and could be overridden to be something else if the actual entityID is not stable.

Or it could just be whatever the property is set to of course with the stipulation that it doesn't mean the IdP ever actually names itself that in a message.

-- Scott