07-17-2019 08:16 AM
According to BRKSEC-3697 and a previous forum post, RSA passcode caching is NOT replicated between PSNs.
My question is NOT regarding passcode caching however but RSA Identity Caching.
Is Identity Caching replicated between PSNs? I presume not but want to clarify.
Associated question, was there any change in Identity Caching behaviour when the ability to modify the aging time was introduced in 2.4 patch 6 (and I believe 2.2 and 2.3 via CSCvk74190; though the BugID only mentions Radius Token Identity Caching, I assume it applies to RSA also). It's disabled by default and I assume was enabled (but unconfigurable) pre-patch. But otherwise, any changes?
Solved! Go to Solution.
07-18-2019 04:03 PM
Is Identity Caching replicated between PSNs? I presume not but want to clarify.
Correct. This is not currently replicated.
Associated question, was there any change in Identity Caching behaviour when the ability to modify the aging time was introduced in 2.4 patch 6 (and I believe 2.2 and 2.3 via CSCvk74190; though the BugID only mentions Radius Token Identity Caching, I assume it applies to RSA also). It's disabled by default and I assume was enabled (but unconfigurable) pre-patch. But otherwise, any changes?
Before CSCvk74190 addressed, this is always enabled with the aging timeout hard-coded to 120 seconds (or 2 minutes). Afterwards, the default behavior is no caching (or disabled) but can be enabled and configured with an aging timeout between 1 and 1440 seconds.
07-18-2019 04:03 PM
Is Identity Caching replicated between PSNs? I presume not but want to clarify.
Correct. This is not currently replicated.
Associated question, was there any change in Identity Caching behaviour when the ability to modify the aging time was introduced in 2.4 patch 6 (and I believe 2.2 and 2.3 via CSCvk74190; though the BugID only mentions Radius Token Identity Caching, I assume it applies to RSA also). It's disabled by default and I assume was enabled (but unconfigurable) pre-patch. But otherwise, any changes?
Before CSCvk74190 addressed, this is always enabled with the aging timeout hard-coded to 120 seconds (or 2 minutes). Afterwards, the default behavior is no caching (or disabled) but can be enabled and configured with an aging timeout between 1 and 1440 seconds.
07-19-2019 03:28 AM
Cheers - that's helpful.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide