Access control plugin in Git 5572 add page not displayed

[george1421]

@Tom-Elliott So then do I understand this is not a viable plugin just yet?

I need to limit certain deployment techs to specific storage locations so that techs from site A can’t deploy images or snapins to site B on accident (or intent).

[Tom Elliott]

It is a viable plug in it just is not usable via database.

[Wayne Workman]

@Tom-Elliott Can you describe how it is normally used? Where is the configuration located?

[george1421]

@Tom-Elliott said:

It is a viable plug in it just is not usable via database.

@Wayne-Workman Yeah, this has me a bit confused. I read what Tom said as: its fully functional but you can’t configure it. I checked and I can’t seem to find a wiki on how to set this up.

[Wayne Workman]

@george1421 Oh I’m sure it’s configurable (by editing the PHP that it’s made of)…

[Tom Elliott]

I didn’t describe configuration because it’s not a simple thing to try to explain using a cell phone. When I get home I’ll try to describe more. You can also call out for @Lee-rowlett to see if he can spur in a few dimes.

[Lee Rowlett]

as tom says it is quite difficult to explain entirely, but if you understand how hooks work, then access control works in the exact same way. take a look at /$webroot/fog/lib/plugins/accesscontrol/hooks

Access Control works by “UserType” and at the moment the only way you can set this is via database

the idea would be

User Type 0 = Admin
1 = Creator
2 = Editor
3 = Engineer/User

What you are trying to achieve to stop users imaging from one location when they’re at another, would get complex. unless you have certain engineers who will only ever image from one location then you could go down the route of

Type 0 = Image From any location
Type 1 = Can only image from location A
Type 2 = Can only image from location B

Hope this all makes sense

[george1421]

@Lee-Rowlett Thank you for the clarification. This isn’t meant to be negative, but unfortunately this plugin is not at a level we would be able to use it for what we need. I’m trying to avoid diving into the OS to make changes to the system. I may have to take a step back and look at my multi master model to isolate the sites.

Again thank you for taking time to clarify this.

[Thiago Moraes]

@Tom-Elliott, could you help me to setup the access control?
I’m trying do it, but I don’t know exactly what parameters I need send to hooks.

[Lee Rowlett]

@Thiago-Moraes What is it you’re trying to achieve with access control? be aware it’s not implemented to configure from the web gui but it’s functional

[Thiago Moraes]

Dear guys,

Any news about this topic? Could we try deploy de access control now?

I’d like change the select/sql of mobile page when I search by some host, could you help me find this source code to do it?

[george1421]

@Thiago-Moraes Wow that was about a year ago…

The access control plugin was never really a finished plugin, it was more of a framework where YOU could write some stuff to make it complete. The last I heard the devs were thinking about removing the plugin altogether since it wasn’t functional in its current state.

[Tom Elliott]

@george1421 said in Access control plugin in Git 5572 add page not displayed:

@Thiago-Moraes Wow that was about a year ago…

The access control plugin was never really a finished plugin, it was more of a framework where YOU could write some stuff to make it complete. The last I heard the devs were thinking about removing the plugin altogether since it wasn’t functional in its current state.

That’s exactly what did happen. It has been removed.

[Wayne Workman]

@Thiago-Moraes Here’s my advice for you: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

Joking aside, it looks like you’re on an absolutely ancient version of FOG. I’d recommend you build a new server using the latest FOG 1.3.0 Release Candidate and begin using that.