David Crome
David Crome
I do not remember, what is the problem with the session configuration? I guess we need to persist the session data between restarts.
I did not test it, but I think you are right, the `server.session.timeout` is only working with the standalone configuration. Let's do it like you described.
I think this is obsolete since we want to persist the sessions with Spring Session (#293) and then we can or have to set the timeouts globally @wallner @tkrille
okay, but I think the config is an implicit task of the persist sessions feature.
+:100: thanks for the great explanation!
+1 But the registration is possible with all fields of a SCIM user? What about extensions?
But if we copy the code from the self-administration we can provide the registration endpoint which accepts all scim user fields.
The one who adds this feature, please beware of this feature: https://github.com/osiam/addon-self-administration/issues/67
yes, please support it!
Sorry for the later answer. I don't know if the new one provides both fields, but the old one does: `apt-cache show gitlab-ci-multi-runner` Fun fact 🤣 ``` Replaces: gitlab-runner Provides:...