Konrad Windszus

IMHO this is relevant and would fix https://issues.apache.org/jira/browse/MSHARED-989.

I don't have capacity for this unfortunately.

Adding a link to https://github.com/adobe/aio-lib-ims?tab=readme-ov-file#oauth-server-to-server-configuration would help as well.

Particularly interesting is whether the underlying resourceResolver/session is derived from the user session bound to the request or always an admin or service resource resolver/session.

@royteeuwen Thanks for picking it up, but then I am wondering, what this service user is used for in Groovy Console: https://github.com/orbinson/aem-groovy-console/blob/1100331993e8799f2d6c82223e9950e5d1945fed/ui.config/src/main/content/jcr_root/apps/groovyconsole-config/osgiconfig/config/org.apache.sling.jcr.repoinit.RepositoryInitializer-groovyconsole.config#L8

Compare with the related https://github.com/valtech/aem-easy-content-upgrade/issues/220

Particularly it is not clear when which of the three service users from https://github.com/valtech/aem-easy-content-upgrade/blob/c5bce3e529dffe77683f7873f896472f78d861ef/complete/src/main/content/jcr_root/apps/valtech/aecu-complete/config/org.apache.sling.jcr.repoinit.RepositoryInitializer~setacls.config#L14-L24 are used from where.

The meta data in GitHub need to be fixed as well: 

@gnodet Is this going in the right direction? A lot of work still to be done....

You should not overwrite m-javadoc-p and m-compiler-p configuration with regards to target bytecode/API version in https://github.com/apache/incubator-xtable/blob/15cc0f8b536b7b5ead16561c49df4ffcd0b36ee4/pom.xml#L891 and https://github.com/apache/incubator-xtable/blob/15cc0f8b536b7b5ead16561c49df4ffcd0b36ee4/pom.xml#L609. This is all done in ASF parent according to the property value...