Disable access to Mango for non Admin clients - DGLux access only.
We have our Mango installation set up so that when you access the login page it directs you to the DGLux login page.
When logging out of DGLux the user is redirected back to the DGLux login page.
The problem is if you enter an invalid URL or a Mango URL you get sent through to Mango.
How can I disable non administrator access to Mango, only allowing DGLux access to clients? I don't want our clients getting into Mango and re-configuring data points, etc.
You should be able to configure this in the /web/modules/dglux/classes/dglux.properties file as long as it's a recent version of Mango.
I have used the dglux.properties file to modify the login page and redirection.
The problem is how do I disable access to Mango?
If a client logs in to DGLux they get a URL of <hostname>/dglux/view
If they changed that to <hostname>/blah they would get the Mango page not found page with access to many parts of Mango.
Here is how it works in my test in 2.5.2. In my dglux.properties file I have:
#Options for login page: mango (Normal Mango Login), dglux (DGLux Login Page) loginPage=dglux #Options for login redirection: default (Mango Default URI), /dglux/view (direct into DGLux), any page view #Note: this only works if the loginPage is set to use dglux loginRedirect=/dglux/view
When I go to the root URL I get the DGLux login. When I log out of either Mango or the DGLux app I go back to the login.
If when I am logged in go to the root URL I get the Mango Watch list or other page I was last on within Mango.
Does this line up with what you are seeing. I think what you want is for the root URL to always go back to DGLux. It might be an easy fix but figuring out which page within DGLux to alway go to if the user is logged in might not be easy. Maybe a default URL in the dglux.properties file would work for this.
Yes, my dglux.properties file looks the same with the addition of a logout redirect.
Is it possible to run DGLux on a different port or web server service, essentially isolating it from Mango?
Obviously I will still need access to Mango for administration purposes.
No, you can't run it on a different port. I don't think there is a good solution except for some code changes in the module that might be possible. I'm not sure when we can look at it but I'll put it on our list.
Can I disable access to all modules except DGLux for non admin users?
If I log in to Mango as a non admin user currently I am able to modify data sources and cause all sorts of havoc.
If that is the case you have not set up your user permissions correctly. Make sure you don't have the whole "check box" selected by any of the data sources and rather just give them read or set permission. This way the only thing they will see are basic modules such as watch list, point details. We are working on improving the user permission so its easier to customize and some of this will be available in 2.6 soon.
That was it. I had completely misinterpreted what the check boxes were for and had them selected. That resolves the issue of clients causing havoc but it would be nice to remove access to all modules except DGLux.
I'm looking forward to the next version. Development seems to be happening in leaps and bounds lately. I especially like the new module upgrade feature.