| Summary: | Add support for LDAPS | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Magnus Enger <magnus> |
| Component: | Authentication | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | dcook, dpavlin, f.demians |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Magnus Enger
2020-05-15 12:59:07 UTC
I'm encountering the same issue with Google Workspace LDAP server. It is necessary to explicitly specify Google cert/key files generated for each configured LDAP client from Google Workspace admin console. Something like that: clientcert => '..../etc/ldap/Google_xx_yy_zz_36497.crt', clientkey => '..../etc/ldap/Google_xx_yy_zz_36497.key', |