-
Type:
Enhancement
-
Status: Resolved (View Workflow)
-
Priority:
Blocker
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 1.1.0.CR5, 1.2.0.Beta1
-
Component/s: HTTP
-
Labels:None
-
Environment:
#
Currently the SpnegoAuthenticationMechanism caches against the connection scope and uses the cached GssContext to recreate the identity.
We should consider the following: -
- Using the same cached identity mechanism as is used by FORM authentication.
- Adding configuration to specify which scope to cache against.
- Add an option to disable caching entirely, this would need to take into account cases where continuation is required as that would become unsupported.
- is duplicated by
-
ELY-1314 Elytron, make scope of SPNEGO authentication configurable
-
- Resolved
-
- is incorporated by
-
JBEAP-12460 Elytron, make scope of SPNEGO authentication mechanism configurable
-
- Verified
-