You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/03/02 17:04:00 UTC
[jira] [Updated] (SLING-11171) WARN "The provided service user id 'serviceuser--org.apache.sling.auth.core'" is not a known JCR system user id and therefore not allowed in the Sling Service User Mapper."
[ https://issues.apache.org/jira/browse/SLING-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-11171:
------------------------------------
Description:
The warning is emitted when launching the Sling Starter and seem to be related to SLING-9622. Is a service user configuration now required? Why is it falling back to such a weird user id in case no mapping is provided?
{code}
02.03.2022 17:54:11.343 *WARN* [pool-10-thread-1] org.apache.sling.jcr.resource.internal.JcrSystemUserValidator The provided service user id 'serviceuser--org.apache.sling.auth.core' is not a known JCR system user id and therefore not allowed in the Sling Service User Mapper.
{code}
was:The warning is emitted when launching the Sling Starter and seem to be related to SLING-9622. Is a service user configuration now required? Why is it falling back to such a weird user id in case no mapping is provided?
> WARN "The provided service user id 'serviceuser--org.apache.sling.auth.core'" is not a known JCR system user id and therefore not allowed in the Sling Service User Mapper."
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-11171
> URL: https://issues.apache.org/jira/browse/SLING-11171
> Project: Sling
> Issue Type: Bug
> Components: Starter
> Affects Versions: Starter 12
> Reporter: Konrad Windszus
> Priority: Major
>
> The warning is emitted when launching the Sling Starter and seem to be related to SLING-9622. Is a service user configuration now required? Why is it falling back to such a weird user id in case no mapping is provided?
> {code}
> 02.03.2022 17:54:11.343 *WARN* [pool-10-thread-1] org.apache.sling.jcr.resource.internal.JcrSystemUserValidator The provided service user id 'serviceuser--org.apache.sling.auth.core' is not a known JCR system user id and therefore not allowed in the Sling Service User Mapper.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)