Topic Thread

Expand all | Collapse all

Disambiguation ID question for CA Secure Cloud

Jump to Best Answer
  • 1.  Disambiguation ID question for CA Secure Cloud

    Posted 02-12-2015 11:05 AM

    How was the AWS issue resolved in 1.52? Is it by the new Disambiguation ID?

     

    In the past, we use one local EntityID for all tenants and all SaaS for federation. Can we continue to do the same? Or, shall we create individual local EntityID for each tenant/SaaS?



  • 2.  Re: Disambiguation ID question for CA Secure Cloud
    Best Answer

    Posted 02-12-2015 11:08 AM

    AWS problem is addressed by introducing disambiguation ID. Actual problem was in that CA Secure Cloud was not able to connect to multiple SAML 2.0 local entities that use the same entity id with a single target remote entity, so we needed distinct name to address this and hence introduced Disambiguation ID. So now you need to create individual local entities (having same entity IDs and different Disambiguation ID) per Tenant basis.