|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 3467 | minor | always | 04-29-09 14:23 | 08-27-09 19:17 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.0 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.2 | ||
|
|
|||||
| 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? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||