Axel Faust

The module already supports and hooks into the default Alfresco synchronization subsystem. There is no need for a separate cron config property because that is what `synchronization.import.cron` does. Provided you...

The default regular Alfresco synchronization happens once per day (at midnight), unless a new / unknown user logs in. So the behaviour as you report it would be "expected".

You should adapt the Alfresco property `synchronization.import.cron` in this case. Simply set a cron that i.e. executes a synchronization every few hours (I have a customer who has it set...

The error message is reported from within the Keycloak adapter libraries themselves, not any code written specifically by me. The package name `de.acosix.alfresco.keycloak.deps` denotes Keycloak libraries that have been repackaged...

Hmm... you have a message in there that points to the problem: `Invalid type keycloak specified for Authentication subsystem. No context file found` This means that the Keycloak module is...

So - the files in the `src/test/docker/alfresco` path aren't all meant to be put 1:1 into the Tomcat shared classpath. For one, they are specific to the test setup in...

So the beans of the classes listed only exist within the Keycloak authentication subsystem, which is a child application context of the regular Alfresco Spring context. This is why you...

While you can potentially use the JWT token used for authenticating a user in Alfresco to call another service, in a clean / secure Keycloak setup, this would/should not be...

This is a kink of the implementation by Alfresco - if the ticket has not yet been retrieved / validated / created within the current request, it is not stored...

Note: The "wontfix" label applies to the specific way the change in this PR is done, not to the idea behind it. As outlined in #18 I plan to work...