0a05a091d8
server: split off modify requests from ldap_handler
2025-04-09 09:30:39 +09:00
6a2a5fe7f5
server: split off create_* from ldap_handler
2025-04-09 09:30:39 +09:00
52f22c00c3
server: split off compare from ldap_handler
2025-04-09 09:30:39 +09:00
37a85b4c2e
server: split off password handling from ldap_handler
2025-04-09 09:30:39 +09:00
63f8b51c88
server: split off do_bind from ldap_handler
2025-04-09 09:30:39 +09:00
c4aca0dad7
server: split off ldap/search from ldap_handler
2025-04-09 09:30:39 +09:00
b8f114bd43
ldap: add support for creating groups
2025-04-08 19:15:47 -05:00
ba9bcb3894
chore: Migrate all the crates to edition 2024
2025-03-30 21:32:46 -05:00
5afcdbda65
app, server: Add an endpoint to fetch the frontend settings
2025-03-30 20:52:39 -05:00
e4044b7415
dependencies: Upgrade sea-orm to 1.1.8
2025-03-30 23:00:50 +02:00
2a226963ee
auth: move Permission and ValidationResults to auth crate
2025-02-22 23:18:06 +01:00
ca1c6ff645
domain-handlers: move backend handler traits to separate crate
2025-02-21 20:41:20 +01:00
d854ace89f
domain-model: move domain::model module to separate crate
2025-02-21 10:25:07 +01:00
5d2f168554
domain + server: introduce new AttributeValue enum
2025-02-19 15:48:27 +01:00
8285e21ebb
domain: rename AttributeValue to Attribute
...
Preparation for storing the actual types for each value, which
will repurpose the AttributeValue name.
2025-02-05 16:07:05 +01:00
4c6cfeee9e
server: remove deprecated fields from CreateUserRequest
...
The fields first_name, last_name, and avatar have all been moved
to regular attributes in the database, and are available through
the GraphQL API as such as well. This commit removes the legacy
fields for each on the internal CreateUserRequest type, leaving
these to only be updateable through attributes.
The fields are still available in the GraphQL CreateUserInput
type, preserving backwards compatiblity, and if set, they will
be used for the corresponding attribute values. If both fields
and attributes are set, the values given through attributes will
superceed the fields, and be used. This change also fixes a bug,
where creation of a user would fail if either of these attributes
were set as both attribute and field, as it would attempt to
insert the attribute twice, violating a unique constraint in the
database.
2025-02-05 15:42:06 +01:00
dd0ba5975e
server: Adds support for whoamiOID
...
Co-authored-by: eyjhb <eyjhbb@gmail.com >
2025-02-03 23:21:44 +01:00
1b26859141
server: move domain::types to separate domain crate ( #1086 )
...
Preparation for using basic type definitions in other upcoming
modules, in particular for plugins.
2025-02-03 23:00:27 +01:00
417abc54e4
server: Cleanup log messages for ignored attribute warnings
...
Reduce log messages by remove line break and remove visible \n\ sequence
2025-02-03 22:52:15 +01:00
c01c7744c7
server: fix a couple of clippy warnings
2025-01-29 13:32:05 +01:00
1b58ac61f4
server: fix serving of frontend after PR #1079 ( #1090 )
...
Had changed behaviour to serve the gz compressed wasm package
with the uncompressed handler.
2025-01-29 13:25:03 +01:00
f46e5375df
server: Allow custom path to front-end assets
2025-01-28 19:37:12 +01:00
0799b6bc26
server: include preserved case in user attribute value search
...
Extends the generated UserRequestFilter with an OR'ed clause for
the attribute value in both it's original case and lowercased.
2025-01-22 10:37:04 +01:00
f5fbb31e6e
server, app: Add validation for attribute names ( #1075 )
...
This commit adds support for basic validation of attribute
names at creation, and also in the schema overview. Both
user and group attributes are validated with the same rules.
For now, attribute names will be considered valid, if they
only contain alphanumeric characters and dashes.
Validation has been added the following places:
- In graphql API, for creation of both user and group attributes.
Request will be rejected, if attribute name is invalid.
- In frontend, before submitting a request to create a new user
or group attribute. Rejection here will show an error message
including a list of the invalid characters used.
As this change adds stricter validation to attributes, and, since
the rationale for this is partly compatibility with other LDAP
systems, this change also adds a warning in the schema overviews
to any attribute using invalid characters.
2025-01-22 09:57:47 +01:00
33fb59f2f7
server: Add support for querying GroupId with LDAP filters
2025-01-20 17:07:53 +01:00
f417427635
Prevent starting up if the JWT secret is not given
...
Similarly, don't create the admin if the password is not given
2024-12-24 19:40:26 +01:00
0ddeab8caa
server: Fix schema migration from v8 for sqlite and postgres
...
Neither supports limits, but we can delete all the duplicate memberships and re-insert a single one
2024-11-21 23:34:37 +01:00
713dbde4cb
server: Fix the instructions to silence the key_seed warning
2024-11-14 22:27:32 +01:00
95337e2cd8
server: Remove session-wide logging, add session_uuid to message logs
2024-11-04 21:47:26 +01:00
143eb70bee
server: Only use a single connection with SQlite
...
Several writer connections can lock the DB and cause other inserts to fail.
A single connection should be enough given the usual workloads
2024-10-30 15:35:47 +01:00
35fe521cbe
server: Correctly handle removal of the display_name attribute
2024-10-29 15:33:46 +01:00
c8601b9169
server: Correctly handle attempts to probe for password resets
2024-10-28 20:09:46 +01:00
f0fcc88f1d
server: Fix env warning for nested keys
2024-10-28 16:23:25 +01:00
c08ddecd32
server: Fix missing lowercasing when changing passwords through LDAP
2024-10-28 16:06:25 +01:00
a190fe7ddf
server: return custom attributes when asked for all attributes
2024-10-26 19:07:08 +02:00
52c917d967
server: improve key_seed warning
2024-10-22 00:48:40 +02:00
f01daae6a8
server: Fix env variable warning
2024-10-22 00:48:29 +02:00
305b272cdf
app: Add support for group attributes
2024-10-22 00:37:38 +02:00
56eee6908e
server: Add a way to print raw logs
...
If the variable LLDAP_RAW_LOG is set, the logs will be both formatted with tracing_forest and printed raw
2024-10-10 21:27:36 +02:00
17bcd7645b
app: Clean up code, don't error on admin empty email
2024-10-05 23:10:40 +02:00
dcba3d17dc
app: Add support for user-created attributes
...
Note: This PR doesn't handle errors around Jpeg files very well.
Co-authored-by: Bojidar Marinov <bojidar.marinov.bg@gmail.com >
Co-authored-by: Austin Alvarado <pixelrazor@gmail.com >
2024-09-30 23:53:14 +02:00
1f3f73585b
server: Add logging for password resets, add name for successful opaque logins
2024-09-26 22:51:34 +02:00
0c6a92a8fa
server: Clarify logging of login attempts and failures
2024-09-26 20:43:19 +02:00
10a820f2a2
server: detect anonymous binds and return a correct error
2024-09-11 22:19:58 +02:00
01f97f5ed4
server: clean up the expected keys
2024-09-10 23:25:33 +02:00
f14aa2284c
server: Detect unknown env variables (e.g. due to typos)
2024-09-08 21:45:36 +02:00
65e2103365
server: Simplify the debug print of various structs
...
And use derive_more more liberally to simplify the impls
2024-09-08 00:43:58 +02:00
5db0072cfa
server: clarify SMTP error message
...
SMTP docs for many email providers use SSL to mean SSL/TLS, and TLS to mean STARTTLS, causing endless confusion. This should hopefully help.
2024-09-07 23:50:43 +02:00
1d8d3eb73f
server: Fix attribute name
2024-09-07 22:27:20 +02:00
6cf0f6df06
server: map email and display_name from attributes into user fields
2024-08-28 00:25:23 +02:00
Valentin Tolmer