In the issue indicated above, the user authentication is failing because the -env option for DOMAINNAME was incorrect. An example of the service definition on which users are NOT able to log in:
sm_service install --force --unmanaged --startmode=runonce \
'--name=PRIMARY_SAM' \
'--description=EMC Smarts SAM Notification' \
'--env=DOMAINNAME=PRIMARY_SAM' \
'--env=SM_SITEMOD=/apps/Presentation/SAM/smarts/local-custom' \
'--env=SM_WRITEABLE=/apps/Presentation/SAM/smarts/local-custom' \
'--env=SM_AUTHORITY=IDENTIFY=sm_authority, AUTHENTICATE=/apps/Presentation/SAM/smarts/local-custom/script/bt/sm_authority.pl' \
'/apps/InCharge8/SAM/smarts/bin/sm_server' \
'--name=PRIMARY_SAM' \
'--config=ics-prsn-npr-n' \
'--port=51283' \
'--ignore-restore-errors' \
'--broker=localhost:426' \
'--dynamic' \
'--output=PRIMARY_SAM.log'
The --env option is used to set environment variables. In this instance the SM_DOMAINNAME was not set and this caused the issue with the login.
The service name used will be that assigned by the --name option and this is what is referred to in sm_service actions. This option is a required option. If SM_DOMAINNAME is not set, then the service name is used.