mirror of
https://github.com/inverse-inc/sogo.git
synced 2026-08-20 06:03:20 +00:00
@@ -425,25 +425,31 @@ Defaults to `YES` when unset.
|
||||
|The location of the SSL private key file on the filesystem that is used
|
||||
by SOGo to sign and encrypt communications with the SAML2 identity
|
||||
provider. This file must be generated for each running SOGo service
|
||||
(rather than host).
|
||||
(rather than host). Make sure this file is readable by the SOGo user.
|
||||
|
||||
|S |SOGoSAML2CertiticateLocation
|
||||
|The location of the SSL certificate file. This file must be generated
|
||||
for each running SOGo service.
|
||||
for each running SOGo service. Make sure this file is readable by the SOGo user.
|
||||
|
||||
|S |SOGoSAML2IdpMetadataLocation
|
||||
|The location of the metadata file that describes the services available
|
||||
on the SAML2 identify provider.
|
||||
on the SAML2 identify provider. The content of this file is usually generated
|
||||
directly by your SAML 2.0 IdP solution. For example, using SimpleSAMLphp, you
|
||||
can get the metadata directly from https://MYSERVER/simplesaml/saml2/idp/metadata.php
|
||||
Make sure this file is readable by the SOGo user.
|
||||
|
||||
|S |SOGoSAML2IdpPublicKeyLocation
|
||||
|The location of the SSL public key file on the filesystem that is used
|
||||
by SOGo to sign and encrypt communications with the SAML2 identity
|
||||
provider. This file should be part of the setup of your identity
|
||||
provider.
|
||||
provider. Make sure this file is readable by the SOGo user.
|
||||
|
||||
|S |SOGoSAML2IdpCertificateLocation
|
||||
|The location of the SSL certificate file. This file should be part of
|
||||
the setup of your identity provider.
|
||||
the setup of your identity provider. Make sure this file is readable by the SOGo user.
|
||||
|
||||
|S |SOGoSAML2LoginAttribute
|
||||
|The attribute provided by the IdP to identify the user in SOGo.
|
||||
|
||||
|S |SOGoSAML2LogoutEnabled
|
||||
|Boolean value indicated whether the "Logout" link is enabled when using
|
||||
@@ -1230,13 +1236,32 @@ documentation of your identity provider and the SAML2 configuration keys
|
||||
that are listed above for proper setup. Once a SOGo instance is
|
||||
configured properly, the metadata for that instance can be retrieved
|
||||
from `http://<hostname>/SOGo/saml2-metadata` for registration with the
|
||||
identity provider.
|
||||
identity provider. SOGo will dynamically generate the metadata based on
|
||||
the SOGoSAML2CertificateLocation's content and the SOGo server name.
|
||||
|
||||
When using SimpleSAMLphp, make sure the convert OID to names by modifying your
|
||||
`metadata/saml20-idp-hosted.php` to contain something like this:
|
||||
|
||||
----
|
||||
'attributes.NameFormat' => 'urn:oasis:names:tc:SAML:2.0:attrname-format:uri',
|
||||
'authproc' => array(
|
||||
100 => array('class' => 'core:AttributeMap', 'oid2name'),
|
||||
),
|
||||
----
|
||||
|
||||
If you want to test the IdP-initiated logout using SimpleSAMLphp, you can do so by opening
|
||||
the following URL:
|
||||
|
||||
----
|
||||
https://idp.example.org/simplesaml/saml2/idp/SingleLogoutService.php?ReturnTo=www.sogo.nu
|
||||
----
|
||||
|
||||
In order to relay authentication information to your IMAP server and if
|
||||
you make use of the CrudeSAML SASL plugin, you need to make sure that
|
||||
_NGImap4AuthMechanism_ is configured to use the `SAML` mechanism. If you
|
||||
make use of the CrudeSAML PAM plugin, this value may be left empty.
|
||||
|
||||
|
||||
Database Configuration
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
||||
Reference in New Issue
Block a user