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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Service User Mapper 1.5.6
• Fix Version/s: Service User Mapper 1.5.8
• Component/s: Service User Mapper
• Assignee: Sagar Miglani
• Reporter: Sagar Miglani
• Created: 21/Jun/23 08:09
• Updated: 21/Aug/23 09:01
• Resolved: 20/Jul/23 05:56

Description

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:

: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"

3) Without changing the configuration click on save, the configuration becomes:

: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"

i.e required.principal.validators and required.user.validators have an empty value and due to this all sling requests return

"HTTP ERROR 503 ServletResolver service missing, cannot service requests".

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)

Issue Links

• relates to: FELIX-6614 WebConsole configMgr saves an empty value in list properites
• links to: GitHub Pull Request #8