View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002463 | SOGo | Web Mail | public | 2013-10-22 19:14 | 2013-10-23 13:13 |
Reporter | vbonamy | Assigned To | |||
Priority | high | Severity | minor | Reproducibility | always |
Status | assigned | Resolution | open | ||
Product Version | 2.0.6b | ||||
Summary | 0002463: SOGo + SSO CAS - CAS session expiration -> CPU 100% | ||||
Description | We have a SOGo with CAS Authentication here. Sometimes, we have SOGo processes that take 100% CPU. Before to kill it, if we make a lsof on the process, we can see something like : | ||||
Steps To Reproduce |
| ||||
Additional Information | CAS Server 3.4.7 | ||||
Tags | No tags attached. | ||||
We investigated more and we found that the request from SOGo to CAS server was like : which returns here an Error 500 on our CAS Server (V. 3.4.7). On CAS server, we have effectively in logs : The corresponding ssue on the CAS is here : So I think that upgrade on v3.4.9 of CAS solves the issue. Here we just upgraded our inspekt libraries (jar) : And now CAS answers correctly an usually cas:authenticationFailure in XML (with HTTP status code 200) And now SOGo forwards correctly the user to the CAS authentication form. |
|
-> the prioriry and severity of this issue can be lower now ; because the cas server must not respond with an Error 500 ... |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2013-10-22 19:14 | vbonamy | New Issue | |
2013-10-23 10:03 | vbonamy | Note Added: 0006161 | |
2013-10-23 10:07 | vbonamy | Note Added: 0006162 | |
2013-10-23 13:12 | ludovic | Assigned To | => jraby |
2013-10-23 13:12 | ludovic | Status | new => assigned |
2013-10-23 13:13 | ludovic | Severity | major => minor |