AnsweredAssumed Answered

Using cache with CA Single Sign On Assertions

Question asked by StPaulPete on Dec 17, 2015
Latest reply on Dec 21, 2015 by Carl_Lum

In the help system for the "Authenticate Against CA Single Sign-On" assertion is this statement, but no elaboration.


"The Authenticate Against CA Single Sign-On assertion also offers advanced features such as caching SSO tokens and multiple authorizations of the token."


Anyone have any experience with caching SSO tokens and how would it be different than using the "Store to Cache" and "Look Up in Cache" assertions, which I can do using the smcontext variables the CA Single Sign-On assertions set?  What "advanced feature" does this assertion have, and how do you use it?


Also, a suggestion to the CA folks.  Someone should take a look at the help page for "Authorize via CA Single Sign-On" assertion, accessed from policy manager.  It says things like "This functionality has now been moved to the file:///C:/Program%20Files/Layer%207%20Technologies/Layer%207%20Policy%20Manager%208.3.00/help/Content/Assertions/_Manage_Cookie_.htm." and "To set a CA Single Sign-On cookie in the future, use the file:///C:/Program%20Files/Layer%207%20Technologies/Layer%207%20Policy%20Manager%208.3.00/help/Content/Assertions/_Manage_Cookie_.htm (see Figure 187 for an example).".  The what?  Seems you're missing some text there.