Database IDs

[Joebeurg]

Hi,

I would like to understand the approach chosen for creating IDs, especially for users and groups. Currently it supports integers which I assume are incremental, for me I prefer setting my own ID for a user/group using UUID, is it possible to make it support setting custom ID when creating a user or a group, I know this could be a huge change that the DB models use integer for IDs, and changing it to string might break existing library adopters

[leodip]

Hi!

For users, there's a Subject field which is a UUID that appears in the sub claim of tokens. That's the OIDC standard external identifier. It's auto generated at creation, not settable. The int64 Id is used in REST API endpoints (like GET /users/{id}).

For groups, the GroupIdentifier is a string you provide yourself when creating the group, so custom identifiers are already supported there. The int64 Id is also used in REST API endpoints.

You're right that allowing custom IDs would require significant changes... creation flow, API validation, uniqueness checks, and potentially breaking changes for existing users. It's unfortunately out of scope for now.

As a workaround, you could store an external system ID as a user attribute if needed!

Thanks,
Leonardo

[Joebeurg]

Make sense.
I did not want to go with the additional externalId field in my DB that's why I asked, haha, but it is fine.
Just asking if there is a discord server for Goiabada to have such small talks or discussions over the library?