Day 60: Security in Dash

Dan Esmail - 3/1/2023

Intro

Now for the main problem, we have. We get data from a PHP file that has all the security data for our information. This tells the data frames who can access what kind of data from the server. Now we are using flask which grabs the data from the PHP file. The file is a SQL connection that grabs what information we need from the database.

Cookies

Since we are bringing in the security data from a PHP file with flask we need to hold it in the session cookies to use for later. Flask has a way to do these with a response that sends the information to the cookie. The data comes in a JSON object that is surrounded by an array. I ended up breaking this apart to send all the information in different cookies. Now that I'm holding onto the data I need to send it to dash

DCC Store

This is where the DCC store function comes into play. With this, I can give an ID to the storage of data. Once I add the callback for the main section of my dash I'm able to hold all of these cookies in the session where dash can handle them. All of my layouts are just imputed into the main dash app. This is fantastic because I can still have access to the DCC store function which is holding my security data. That means I can take that data and use it as a callback to help limit the data frame for certain users. A huge chunk of the project was just figured out in the security portion. Now I can spend more time making the dashboards


Day 1

Day 1