Cloudforms - limiting user access using tagging

[DRS]

Hi

I wonder if I might ask a question re: Cloudforms (and I’m sure this is me doing something wrong)

I’m currently trying to experiment with restricting access to objects based upon tagging.

When I am in Settings -> Configuration -> Access Control I am trying to add tags. When I do this, however, the Save button is dimmed.

Presumably this means there is something else I am missing that enables this. 

If anyone could assist with showing me the error I am making I’d be most grateful.

Also if there are any goods links describing how to limit object access to users using tags I’d also be most grateful.

Thank you.

[Razique]

Hey @DRS thanks for reaching out. I am one of the main developer of this course.

As far as I remember (it has been a couple of years), this is a bug in the product that happened intermittently -- this has to do with a browser issue.

Could you try to access CloudForms in a private window ("incognito" mode) and give it another spin?

If this does not work, I will look into that.

-razique

[DRS]

Hi Razique

Thanks very much for the mail. I tried Firefox in incognito mode and unfortunately it behaves exactly the same. i.e not letting me save.

For info I'm usng the lab from the CL220 course, but have been trying to extend myself by trying other scenarios. The kind of thing I'm tryng is described in a link https://cloudformsblog.redhat.com/2016/10/13/using-tags-for-access-control

Really appreciate your response. Any workaround would be very much appreciated.

Thank you Razique

[Razique]

Hey @DRS 

I'll spin up an environment today and do some testing. I'll get back to you with my findings.

[DRS]

Thank you. Really appreciate your help.

[Razique]

Hey @DRS, I was able to provision a CL220 course and configured my appliance. Unfortunately, this is a bug in the interface, sorry for that :/Selecting or clearing one of these tags leads to a JavaScript errror, which, in turn, prevents the update in memory of the tags that have been selected. The error is still there even if you are trying to assign specific tags to the user before creating it.

I deployed a more recent version of the appliciance, and I confirm that the error is gone.

If you are interested in working with those tags, I can access your application and upgrade the appliance, which should fix the issue. If this is something that you would like, drop a message here and I'll take of that.

I also sent a note to the team about this course, to see how we want to tackle this issue.

[DRS]

Hi Razique. 

Firstly, I just want to thank you so much for helping with this.

If you could upgrade my appliance I'd be most grateful as I'm trying to experiement with limiting user access to VM's.

Can I just check, is the approach I'm trying to use here the best way to limit access to VM's by users (i.e by tagging) or is there a better approach?

Thanks again Raziqe. If you could upgrade my appliance I'd me most grateful.  

[Razique · Accepted solution]

Hey DRS -- could you send me a private message with your application ID? The information appears at the bottom when you provision an environment.

Regarding preventing access to certain machines, you would actually use the third tab that reads "VMs & Templates". From there, clear the checkbox for the VMs or templates for which you would like to prevent access.