View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003066 | SOGo | Web General | public | 2015-01-18 12:56 | 2016-12-29 20:54 |
| Reporter | skug67 | Assigned To | ludovic | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Platform | [Server] Linux | OS | Debian | OS Version | 8 (Jessie) |
| Product Version | 2.2.13 | ||||
| Summary | 0003066: CAS authentication fails/hangs | ||||
| Description | This is very similar to (the same as?) issue 0002408 that was marked close. I'm running CASinoApp as a CAS authentication server. I've checked that it is working to protect web directories in general as well as with an Owncloud installation. But when I try to set up SOGo for CAS authentication is sends me to the CAS login page, but I never get successfully sent back to SOGo. Rather the sogo worker thread in question just sits there and hangs. This happens whether or not I try to make use of the proxy-cas-validate.py script. | ||||
| Steps To Reproduce | Set up CASinoApp as a CAS authentication server. | ||||
| Tags | No tags attached. | ||||
|
The doc says "The first constraint is that the amount of workers that SOGo uses must be higher than 1 in order to enable the C.A.S. service to perform some validation requests during IMAP authentication. A single worker alone would not, by definition, be able to respond to the C.A.S. requests while treating the user request that required the triggering of those requests. You must therefore configure the WOWorkersCount setting appropriately." |
|