pharo application user identity

Hi,

my seaside, zinc and pharo applications had held user information within
the image or a db.
That was enough since the users never needed access to local resources.

Now I am in the need to allow uploaded and storage of data on the
server"s harddrive or a NAS.

I wonder how you guys solve identity related issues.
I recognized a ldap implementation on smalltalkhub.

Is there a documentation/example available on best practices regarding
user directories and such?
Or is it a better idea to replace seaside based user registrations with
solutions like keycloak and implement a single-sign-on infrastructure?

Thank you for any hint!
Sebastian