When you open the Human Task Actor Configuration in the deployable central, you see a list of possible users (I assume it fetches whatever is stored in app-users app-roles properties file)

When you open the Human Task Actor Configuration in the standalone central, you see no such thing (see attachment screen1*)

Then I tried to add a new actor (see screen2*) and that seems to succeed.

Then I close the task properties, and open it again - my user is gone. See screen3.

Is this a bug? Or perhaps a configuration issue?

For completion I am also attaching the configuration:

Startup script:
java -jar rhpam-7.1.0-business-central-standalone.jar \
-s ./application-config-DM.yaml \
-Dorg.uberfire.nio.git.dir='.' \
-Dorg.uberfire.metadata.index.dir='.' \
-Dorg.guvnor.m2repo.dir='.' \
-Dorg.uberfire.nio.git.ssh.cert.dir='.'

YAML config:

swarm:
security:
security-domains:
other:
classic-authentication:
login-modules:
myloginmodule:
code: org.kie.security.jaas.KieLoginModule
flag: optional
module: deployment.kie-wb-webapp.war
management:
security-realms:
ApplicationRealm:
local-authentication:
default-user: local
allowed-users: local
skip-group-loading: true
properties-authentication:
path: /Users/agiertli/Documents/work/jboss-playground/710-rhpam7-eap712-psql/standalone-central/application-users.properties
plain-text: true
properties-authorization:
path: /Users/agiertli/Documents/work/jboss-playground/710-rhpam7-eap712-psql/standalone-central/application-roles.properties
datasource:
management:
wildfly:
admin: admin

app-users.properties file:

rhpamAdmin=password1
controllerUser=controllerUser1234

app-roles.properties file:

rhpamAdmin=analyst,admin,manager,user,kie-server,kiemgmt,rest-all
controllerUser=kie-server

Expected behavior is that the users from the properties file will be loaded/displayed in the standalone central. And the user you add will be preserved.