Tenable.sc help

[Darren Boss]

I don't have direct access to the Tenable instance, just working with
the person that does so I can't answer all questions with certainty
about the configuration.

I'm the person responsible for our IdPs so I'm reverting the additions
made to saml-nameid.xml because the format should be avoided and in
this case, it didn't help at all. 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.

My co-worker is also having a chat with the Tenable sales engineer
today and was going to voice our disappointment in the product
regarding the SAML support and the hours of effort required to get
this working.

On Thu, Jun 24, 2021 at 12:58 PM Cantor, Scott <cantor.2 at osu.edu> wrote:
>
> On 6/24/21, 12:51 PM, "users on behalf of Darren Boss" <users-bounces at shibboleth.net on behalf of darren.boss at computecanada.ca> wrote:
>
> >    We just got it to work using attribute oid instead of the friendly name.
>
> Well, the latter would be a bug, so...I certainly don't think it requires that.
>
> My notes don't suggest there was anything unusual about this except that it had a bug at least at one point in which editing the settings in the GUI inadvertently reset the entityID to something invalid and kept overwriting the value that was put into the configuration to correct it.
>
> There was nothing unusual in my notes regarding use of an Attribute to key it or any other interop issues.
>
> -- Scott
>
>
> --
> For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net



-- 
Darren Boss
Senior Programmer/Analyst
Programmeur-analyste principal
darren.boss at computecanada.ca