You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 679c854
Browse filesBrowse the repository at this point in the historyBrowse files
Simplify the stack and ease integration with other modules like NethVoice.
Changes:
* Add synapse ldap config and remove dex
* Fix element template
* Remove dex from README
- Configure Dex as OpenID Connect provider with LDAP/AD backend
54
-
- Start and configure the Synapse Matrix homeserver with OIDC authentication
51
+
- Start and configure the Synapse Matrix homeserver with LDAP authentication
55
52
- Deploy Element Web client and Cinny client configured to connect to the local Synapse instance
56
53
- Set up Traefik routes for both domains with automatic SSL certificates
57
54
@@ -108,11 +105,11 @@ The Element client supports customized themes, examples are added to the configu
108
105
109
106
### Cinny Client
110
107
111
-
Cinny is an alternative web client for Matrix chat, included in this module to provide users with a modern, lightweight interface. It can be accessed via a web browser and supports essential Matrix features such as messaging, rooms, and user authentication via OpenID Connect. Cinny is pre-configured to work with the Synapse server and Dex for seamless integration with NethServer 8 LDAP.
108
+
Cinny is an alternative web client for Matrix chat, included in this module to provide users with a modern, lightweight interface. It can be accessed via a web browser and supports essential Matrix features such as messaging, rooms, and user authentication via OpenID Connect. Cinny is pre-configured to work with the Synapse server for seamless integration with NethServer 8 LDAP.
112
109
## LDAP Integration
113
110
114
111
The module automatically discovers LDAP settings from the NethServer 8 configuration.
115
-
Dex is configured to connect to the NS8 LDAP proxy to authenticate users against
112
+
Synapse is configured to connect to the NS8 LDAP proxy to authenticate users against
116
113
the centralized user directory.
117
114
118
115
The LDAP discovery happens every time the services start through the `bin/discover-ldap`
@@ -159,29 +156,22 @@ To setup the translation process:
159
156
160
157
Stack explanation:
161
158
-[Synapse](https://element-hq.github.io/synapse/latest/setup/installation.html) is the standard de-fact Matrix homeserver implementation
162
-
- Dex is used as OpenID Connect Provider to authenticate users against LDAP, it's not strictly required unless MAS (Matrix Authentication Service) is used (currently MAS is not implemented in this module)
163
159
- Element web is the official Matrix web client, it can be replaced with other web client clients like [Cinny](https://cinny.in/)
164
160
165
161
Alternative stacks:
166
-
- Remove Dex, use old LDAP integration [matrix-synapse-ldap3](https://github.com/matrix-org/matrix-synapse-ldap3) (currently deprecated
167
-
)
168
162
- Use [MAS](https://element-hq.github.io/matrix-authentication-service/) to add more authentication methods (SAML, OIDC, LDAP, etc.) and integrate with [authentik](https://goauthentik.io/)[1](https://integrations.goauthentik.io/chat-communication-collaboration/matrix-synapse/)[2](https://element-hq.github.io/matrix-authentication-service/setup/sso.html#authentik)
169
163
170
164
### To be done
171
165
172
166
If the current stack will be used, the following must be made.
173
167
174
-
Dex:
175
-
- export preferred user name from LDAP to synapse (currently Dex exports only email and username)
176
-
- add support for LDAP groups (currently Dex exports only users)
- implement authentication, there 2 possible ways:
184
-
- add support for OIDC ID inside [CTI middleware](https://github.com/nethesis/nethcti-middleware): the user authenticate against the Oauth 2 provider (like Dex or authentik, if 2FA is required) and the middleware uses the ID token to authenticate against Synapse with the obtained token
174
+
- add support for OIDC ID inside [CTI middleware](https://github.com/nethesis/nethcti-middleware): the user authenticate against the Oauth 2 provider (like authentik, if 2FA is required) and the middleware uses the ID token to authenticate against Synapse with the obtained token
185
175
- use normal LDAP auhtentication: the CTI middleware takes care also to authenticate against Synapse using LDAP credentials
0 commit comments