User Interface Login Permissions

[me.gonzalez674]

Hello,

My group and I are working on creating a user interface for our professor that allows her students to download to CSV (rather than ICARTT) and interact with SOOT data, without having to do any conversions/data analysis themselves. Essentially, we want a student to be able to select a campaign/PI/year/etc. and create a graph of ozone vs. altitude, or whatever other variable it is. In order to download the files, we know that users must be logged in. With the information sent last time "SOOT API Access," we are able to have people log in by uploading their urs_cookies file. However, this requires students to use their terminal and re-run code to authenticate their session. While this works, the goal of our project is to make this as user friendly for non-computer science/data science/statistics students, and running code in the terminal is not user friendly.

We would like to write code to that allows students to directly input their username and password into our user interface and have the code create this cookies file and authenticate their session in the background. However, we are concerned that there may be some data privacy issues since we are using Streamlit, a third party app. We found a Python script that collects the information, authenticates, and then deletes it after the session. It is not written to disk, just to memory, and is deleted after each session. Since it is your usernames/passwords, we want to check and make sure that we are not causing any problems with this process. Please let us know if this is okay or if you have any follow up questions.

[ASDC - rkey]

Hello @me.gonzalez674,

The SOOT team continues to research your inquiry and will reach out to you with a resolution shortly.

Regards,
Earthdata Forum Team