🐛(backend) allow any string as sub in the API serializer

The API serializer was too restrictive on the `sub` field, expecting
a UUID. This worked in our development and production setups because
our Keycloak is configured to emit UUID subs, but it broke for other
providers.

Per the OIDC spec and the DB model, `sub` can be any string. Align
the serializer with this and accept arbitrary string values.

Fixes #1525.
This commit is contained in:
lebaudantoine
2026-07-27 19:29:42 +02:00
committed by aleb_the_flash
parent 4c57432a03
commit 8c6752a29f
3 changed files with 6 additions and 5 deletions
+2 -2
View File
@@ -297,8 +297,8 @@ class RoomInviteSerializer(serializers.Serializer):
class BaseParticipantsManagementSerializer(BaseValidationOnlySerializer):
"""Base serializer for participant management operations."""
participant_identity = serializers.UUIDField(
help_text="LiveKit participant identity (UUID format)"
participant_identity = serializers.CharField(
help_text="LiveKit participant identity (matching the user's sub format)"
)