Using this Profile.tmp file (obfuscated): export DEBUG=1 export UAA_DEFAULT_USER_EMAIL=<user-email> export UAA_DEFAULT_USER_PW='supersecret' export UAA_DEFAULT_USER_FIRSTNAME='John' export UAA_DEFAULT_USER_LASTNAME='doe' I get the following output: [cloudbreak@cbdeployerVM cloudbreak-deployment]$ CBD_DEFAULT_PROFILE=tmp cbd util add-default-user [DEBUG] Using profile tmp [DEBUG] Cloudbreak Deployer 2.4.0 [DEBUG] Add default admin Cloudbreak user [DEBUG] nameservers on host: xxx.xxx.xxx.xxx [DEBUG] bridge=xxx.xxx.xxx.xxx [DEBUG] DOCKER_CONSUL_OPTIONS= -recursor xxx.xxx.xxx.xxx [DEBUG] Adding user to group openid [DEBUG] Adding user to group cloudbreak.networks [DEBUG] Adding user to group cloudbreak.securitygroups [DEBUG] Adding user to group cloudbreak.templates [DEBUG] Adding user to group cloudbreak.blueprints [DEBUG] Adding user to group cloudbreak.credentials [DEBUG] Adding user to group cloudbreak.stacks [DEBUG] Adding user to group sequenceiq.cloudbreak.admin [DEBUG] Adding user to group sequenceiq.cloudbreak.user [DEBUG] Adding user to group cloudbreak.events [DEBUG] Adding user to group cloudbreak.usages.global [DEBUG] Adding user to group cloudbreak.usages.account [DEBUG] Adding user to group cloudbreak.usages.user [DEBUG] Adding user to group periscope.cluster [DEBUG] Adding user to group cloudbreak.recipes [DEBUG] Adding user to group cloudbreak.blueprints.read [DEBUG] Adding user to group cloudbreak.templates.read [DEBUG] Adding user to group cloudbreak.credentials.read [DEBUG] Adding user to group cloudbreak.recipes.read [DEBUG] Adding user to group cloudbreak.networks.read [DEBUG] Adding user to group cloudbreak.securitygroups.read [DEBUG] Adding user to group cloudbreak.stacks.read [DEBUG] Adding user to group cloudbreak.sssdconfigs [DEBUG] Adding user to group cloudbreak.sssdconfigs.read [DEBUG] Adding user to group cloudbreak.platforms [DEBUG] Adding user to group cloudbreak.platforms.read Default user created. [DEBUG] kill all exited container labeled as: cbreak.sidekick It seems the user is added to lots of groups, however after logging in into the UI I see this: No resources are available to the new user. ... View more

@pdarvasi Thank you for your response. Using the method above I was able to add an additional admin user, however this user has no access to any of the Cloudbreak resources such as the credentials or the already deployed clusters. Can I edit the permissions so that this user can start and stop the existing clusters? ... View more