Add additional users to cloudbreak UI 2.4

[#1]

In the previous version of cloudbreak, users could be invited by e-mail and gain access to the cloudbreak UI. I cannot find any usermanagement in the current version of the cloudbreak UI. How can I add additional users to manage the created clusters?

[#2 · Accepted solution]

@Folkert de Vries

Multi-user management support is not part of Cloudbreak 2.4 version, it is on the roadmap.

One option is to integrate your Cloudbreak deployment with your LDAP instance if you have one, it works the same way in 2.4.

Another option, if you would like to just add another admin user, you can do the following:

• add the following for the new user to a file called Profile.tmp inside cloudbreak deployment directory (/etc/lib/cloudbreak-deployment by default)

export UAA_DEFAULT_USER_EMAIL='[default admin email address]'
export UAA_DEFAULT_USER_PW='[default admin password]'
export UAA_DEFAULT_USER_FIRSTNAME='[default admin first name]'
export UAA_DEFAULT_USER_LASTNAME='[default admin last name]'

• run the following command from the existing Cloudbreak deployment directory

CBD_DEFAULT_PROFILE=tmp cbd util add-default-user

This will create a new admin user and leave the original user and profile untouched.

Hope this helps!

[#3]

@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?

[#4]

It should have been created as an admin user already with those capabilities.

Such capabilities are mapped to so called UAA groups in Cloudbreak, which are shown in debug mode. Here is the relevant code snippet.

Could you retry please, but with an "export DEBUG=1" as a first step and attach the output to this case?

[#5]

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.

[#6]

@Folkert de Vries

Unfortunately it turned out that all the resources are private by default, so they cannot be shared inside an account. The multi-user account mgmt. is on our roadmap.

Sorry for the inconviniences caused!

[#7]

Hi @pdarvasi,

Currently i'm using Cloudbreak 2.7.0, i have enabled LDAP authentication for Cloudbreak UI. I would like to know whether resources can shared in version 2.7.0 and if so could you please help me reference articles on how to setup resource sharing?

Thanks in Advance!

[#8]

Hi @pdarvasi,

Can I create role based multiple users for Cloudbreak UI in cloudbreak 2.5.0?

[#9]

Hi @Marshal Tito, unfortunately there is no option from 2.0 to 2.7 (latest at that time) to organize roles and accounts. You have two options:

• Wait for the feature which is on the way
• Use 1.16.x until the feature arrives in version 2