Drive/roundcubemail-plugins-kolab
0
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix typos

Browse source
This commit is contained in:
Aleksander Machniak 2019-10-10 09:08:43 +02:00
parent d8443212cd
commit 0877e13e47
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
plugins/kolab_sso/README
View file

@ -50,7 +50,7 @@ Limitations:
- supported signature algorithms: HS256, HS385, HS512, RS256, RS384, RS512. - supported signature algorithms: HS256, HS385, HS512, RS256, RS384, RS512.
- supported token endpoint auth methods: client_secret_basic, client_secret_post. - supported token endpoint auth methods: client_secret_basic, client_secret_post.
[IMAP] Because Kolab backend do not support token authentication it is required [IMAP] Because Kolab backend does not support token authentication it is required
to use master user (sasl proxy) authentication, i.e. you have to put to use master user (sasl proxy) authentication, i.e. you have to put
master user credentials in plugin's config. master user credentials in plugin's config.
@ -58,7 +58,7 @@ master user credentials in plugin's config.
you have to specify SMTP connection parameters/user+password. you have to specify SMTP connection parameters/user+password.
[LDAP] Global addressbook (read-only) requires LDAP user/password. 'user_specific' option does [LDAP] Global addressbook (read-only) requires LDAP user/password. 'user_specific' option does
not work as well as proxy authentication. not work, neither the proxy authentication.
[Freebusy] Authentication into kolab-freebusy service is not yet implemented. A solution for [Freebusy] Authentication into kolab-freebusy service is not yet implemented. A solution for
now is to add Roundcube host(s) into trustednetworks.allow option in kolab-freebusy service config. now is to add Roundcube host(s) into trustednetworks.allow option in kolab-freebusy service config.