| Summary | Ingo supplying timsieved with wrong Password |
| Queue | Ingo |
| Queue Version | 1.1.1 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | darron (at) nonfiction (dot) ca |
| Created | 08/03/2006 (6992 days ago) |
| Due | |
| Updated | 08/03/2006 (6992 days ago) |
| Assigned | |
| Resolved | 08/03/2006 (6992 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Not A Bug
won't even get to that part of the code. And if you have set hordeauth
you want to authenticate as the current user, not as the cyrus user.
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Ingo supplying timsieved with wrong Password
Queue ⇒ Ingo
ended up changing this:
if (!empty($_SESSION['ingo']['backend']['hordeauth'])) {
$username = ($_SESSION['ingo']['backend']['hordeauth'] === 'full')
? Auth::getAuth() : Auth::getBareAuth();
// $password = Auth::getCredential('password');
$password = $_SESSION['ingo']['backend']['params']['password'];
What was happening was that Ingo was supplying the:
1. Cyrus admin user's username
2. Effective user's password
That was the problem - once we got it to use the right Cyrus admin
user's password - it works like a charm.