I was thinking more like service=xmpp,service=mastodon and so on. Later, it will also need extra attributes for which namespace of which service it is.
All working in production now! You can try it out yourself.
Not sure what you mean. We can just use attributes to know if a user has access to a certain service or not.
App is now compiled to release dir: https://github.com/67P/akkounts-api/pull/6
So a decent integration always supports a custom "filter" config, which can be filled with the desired attributes, in order to select users that are allowed to use that service. Saw that in the GitLab doc as well.
I'd go with api.accounts.kosmos.org, because the front-end is hosted on accounts.kosmos.org.
This contains interesting information, even when not using GitLab: https://docs.gitlab.com/ee/administration/auth/ldap.html
Greg and I looked at a bunch of options, and we're now testing 389 Directory Server.