According to this Enhanced Session Assurance with DeviceDNA™ – CA Single Sign-On – 12.8 – CA Technologies Documentation you can’t use Enhanced Session Assurance when using SSO zones.
Is there any explanation as to why? Or a recommended way to leverage it if we are using SSO zones or am I really expected to use a single default SM zone?
Seems like a pretty big gap to give us these independent “features” that can’t play nicely together. We really want to implement it but if that’s true it’s a non-starter and I’ve got to find other ways or products : / .
Source: New feed
{pubDate}