Tenable.sc help

Cantor, Scott cantor.2 at osu.edu
Fri Jun 25 15:26:45 UTC 2021

On 6/25/21, 11:05 AM, "users on behalf of Darren Boss" <users-bounces at shibboleth.net on behalf of darren.boss at computecanada.ca> wrote:

>I think we were also seeing the
> issue with not being able to set the entityID and it was just
> defaulting to tenable.sc and at least for now with this SP and it
> using our development IdP, it is fine for the time being.

That's what I don't allow, because that entityID would apply to any tenable deploy in the world, which defeats the purpose; it's not unique, aside from not even being a URL.

If they had a single cloud presence behind a URL that's global, that's fine, but we could have two instances locally for dev/prod and they'd both end up with that entityID. If we wanted that, fine, but for the product to enforce it is not acceptable.

In this case, it's a bug, not deliberate. They just screwed up the interface and it overwrites it every time you save them. Until you save them, you can customize the entityID within SimpleSAML in the usual way.

-- Scott

More information about the users mailing list