Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

  • Jared,

    Thank you so much for putting all this effort into these new features!!

    It looks like they work with the new UI but not the old dashboard pages, which I believe Joel warned us about.

    As soon as get the chance to transfer our pages over, I'll be able to fully test these. My initial tests show they work just fine however.

    I'm pretty excited about these changes.

    Thanks again.


  • @mihairosu You could create a dashboard in the new UI that simply redirects to the old page. When you hit the new UI page you will be logged in then redirect.
    e.g. just put this in the markup

    <meta HTTP-EQUIV="REFRESH" content="0; url=/legacy_page.htm">
    

    P.S. this isn't valid markup but it seems to work (it should go in the head). You could also just use a script tag and set window.location.


  • Hi @Jared, have been trying to implement the auto login feature for the last day or so. Getting slightly annoyed with the auto login local not compatible with the admin template single page app (only just read in one of your other posts in May that it's deprecated which doesn't help me much here now that I am now up to my neck in it.)
    Are you willing to provide some assistance here so I can work out how to implement the cookie type browser storage so that individual users can set an auto login if they wish to? Not so fond of the url type implementation.


  • @MattFox The latest adminTemplate should work with the autologin, what version are you using?

    You will need to enter the credentials at /ui/administration/auto-login-settings but after that the adminTemplate should log you in automatically.


  • Morning Jared, apologies for the late reply, Friday through Sunday seemed to move as one giant blur...
    It's more the fact I'm trying to do multiple custom dashboards. These dashboards each possess their own login for separate users and display different data. There is no wish for them to be able to access the /ui backend as some of the dashboards coded are used for realtime data display on a tv for example.

    However, it would be nice to be able to implement the same code for this into the custom dashboards so that users can configure an auto-login should they wish to.

    Thanks again for your time

    Matt


  • @mattfox said in Guest Login, Permissions and Kiosk Dashboards:

    It's more the fact I'm trying to do multiple custom dashboards. These dashboards each possess their own login for separate users and display different data. There is no wish for them to be able to access the /ui backend as some of the dashboards coded are used for realtime data display on a tv for example.

    The fact that you need display different data for different users should not preclude you from using /ui. You can hide menu items for different users, set permissions on data points and set user's home pages.

    If you setup the main /ui app this way it will save you a lot of time maintaining separate custom applications.

    @mattfox said in Guest Login, Permissions and Kiosk Dashboards:

    However, it would be nice to be able to implement the same code for this into the custom dashboards so that users can configure an auto-login should they wish to.

    If you still want to make separate applications you can copy the autoLoginSettings component from the ui/components folder into your custom app. You will need to register it as part of the application in app.js. This component just displays a username/password form and saves the credentials to local storage/cookies.

    The actual auto-login code is in the User service and is called from the bottom of app.js. You can change the prefix that it is used to store/retrieve data from local storage if needed, let me know if you do.


  • @jared-wiltshire said in Guest Login, Permissions and Kiosk Dashboards:

    The fact that you need display different data for different users should not preclude you from using /ui.

    I wish that were the case, but I am not using angular material based components to display data in these instances and thus have had to make my own point queries to pull the data through and parse it into a format to suit the interfaces I have made.
    I'll definitely take you up on that offer of changing the prefix. Chances are i'm going to need to do it at some point.


  • @mattfox said in Guest Login, Permissions and Kiosk Dashboards:

    @jared-wiltshire said in Guest Login, Permissions and Kiosk Dashboards:

    The fact that you need display different data for different users should not preclude you from using /ui.

    I wish that were the case, but I am not using angular material based components to display data in these instances and thus have had to make my own point queries to pull the data through and parse it into a format to suit the interfaces I have made.
    I'll definitely take you up on that offer of changing the prefix. Chances are i'm going to need to do it at some point.

    OK fair enough then.

    So if you look at ngMango/ngMangoServices.js you will see the config() block configures localStorageServiceProvider with a prefix. You just need to add that to the config block in your app.js, this will ensure the local storage for each of your apps will work independently.


  • Many thanks for dealing with my selfish whims Jared, have a great afternoon. Watch this space!


  • That appears to have done it! Thanks Jared!