Anonymous | Login | Signup for a new account | 12-17-2024 10:35 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0003467 | [Resin] | minor | always | 04-29-09 14:23 | 08-27-09 19:17 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 4.0.0 | ||||||
Summary | 0003467: ClusterSingleSignon | ||||||||
Description |
(rep by Scott Hernandez) The default logon authenticators create an instance of ClusterSingleSignon for use but this causes a problem as every time something is put in cache it is null (the update count is zero on the update query at MnodeStore.java:539). This seems to invalidate "sessions" as every time you come back to get your Principal it is empty. I was able to explicitly change to using the MemorySingleSignon and that fixed the problem (no mnode cache/db/table write problems), but this might be a bug somewhere. Also, where would I configure which single signon instance is used in the configuration for my webapp? |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
30 total queries executed. 26 unique queries executed. |