Axel Faust

The root cause of this issue is that https://github.com/Alfresco/alfresco-community-repo/blob/master/repository/src/main/java/org/alfresco/repo/security/authentication/AuthenticationComponentImpl.java#L134 is not using the normalised user name, but the user name as provided during authentication. The normalisation of the user name...

The reason for this is that changes to nodes exposed via smart folders have always had additional restrictions / checks applied to them. In essence, most update permissions are intrinsically...

The handling in Alfresco for `alf_ticket` is a bit weird, since it is a web script-only feature. In a configuration where `keycloak.authentication.sso.enabled=false` is used, I would not expect any issue,...

So far I cannot reproduce any issue with any default Alfresco web script using a request that contains both `Bearer` and `alf_ticket`. In order to evaluate the necessity and effectivity...

I am sorry to reply so late but the last 1.5 years have seen a bit of a turmoil in my personal life. I have used the latest published version...

@willisplummer The unrecognised property exception was fixed in the recent change that introduces ACS 23.1 compatiblity via #44

@willisplummer You are not dense - the main branch has just changed the minimum required Java version to Java 17 in the context of the ACS 23.1 compatiblity change. It...

Yes, it would be possible for an access token obtained via a client credentials grant to authenticate against Alfresco with a bearer token authentication. But a user with a matching...

A fix for this would require custom serialisation to write out the access and ID tokens as a JSON string, which is a serialisation form naturally supported.

@napetersen That error searching for users is a known bug in Alfresco: https://github.com/Alfresco/acs-community-packaging/issues/367 In the log output you have the message `3 from total count of 3 not processed due...