[jira] [Created] (SLING-11912) Empty configuration in ServiceUserMapperImpl's Required Principal/User validators results in 503

["Sagar Miglani (Jira)" <ji...@apache.org>]

Sagar Miglani created SLING-11912:
-------------------------------------

             Summary: Empty configuration in ServiceUserMapperImpl's Required Principal/User validators results in 503
                 Key: SLING-11912
                 URL: https://issues.apache.org/jira/browse/SLING-11912
             Project: Sling
          Issue Type: Bug
          Components: Service User Mapper
    Affects Versions: Service User Mapper 1.5.6
            Reporter: Sagar Miglani


1) In webconsole configuration manager, open {{Apache Sling Service User Mapper Serviceorg.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl}}
2) Before making any change the configuration is:
{code:xml}
:org.apache.felix.configadmin.revision:=L"1"
require.validation=B"true"
service.pid="org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl"
user.enable.default.mapping=B"false"
{code}
3) Without changing the configuration click on {{save}}, the configuration becomes:
{code:xml}
:org.apache.felix.configadmin.revision:=L"8"
require.validation=B"true"
required.principal.validators=[ \
  "", \
  ]
required.user.validators=[ \
  "", \
  ]
service.pid="org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl"
user.default=""
user.enable.default.mapping=B"false"
{code}
i.e {{required.principal.validators}} and {{required.user.validators}} have an empty value and due to this all sling requests return
{code:xml}
"HTTP ERROR 503 ServletResolver service missing, cannot service requests".
{code}
This persistence of empty configuration seems to be behaviour of {{felix.webconsole}}. But IMO sling requests should not fail due to empty values.

(The above scenario was reproduced in an AEM instance)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)