Support for password fields! Just pass type="password" to st.text_input().
Notable fixes:
Numerous st.cache improvements, including better support for complex objects.
Fixed cross-talk in sidebar between multiple users.
Breaking changes:
If you’re using the SessionState hack Gist, you should re-download it!
Depending on which hack you’re using, here are some links to save you some
time:
If anyone’s up for sharing, I’d be curious to hear how folks are planning to use the password fields.
Are you authenticating with some service external to your Streamlit app?
Or authenticating with your Streamlit app itself (so you’ve got users and password hashes stored somewhere, and don’t show the user your content until they authenticate…)? Any thoughts about security specific to using Streamlit that way?
Following up on David’s question for anyone having users log in: how are you planning to keep track of who is logged in for a given session between reloads?
I could imagine using the session state gists… or leaving the password encoded in the page at each reload. But if anyone has a better approach, I’d love to hear it.
I capture a user name with a text box, and save in a SessionState attribute on startup. Having a valid name disables the prompt on reruns.
As it is an internal site and inside our firewall the password isn’t essential - eventually we’ll want a single sign mechanism either in Streamlit or through some proxy/rerouting.
At some point we may control who can see what content through the user name, but that’s another lookup table for Department/Role and something we’d want to retrieve through LDAP[S] or something similar.
Thanks for stopping by! We use cookies to help us understand how you interact with our website.
By clicking “Accept all”, you consent to our use of cookies. For more information, please see our privacy policy.
Cookie settings
Strictly necessary cookies
These cookies are necessary for the website to function and cannot be switched off. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
Performance cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us understand how visitors move around the site and which pages are most frequently visited.
Functional cookies
These cookies are used to record your choices and settings, maintain your preferences over time and recognize you when you return to our website. These cookies help us to personalize our content for you and remember your preferences.
Targeting cookies
These cookies may be deployed to our site by our advertising partners to build a profile of your interest and provide you with content that is relevant to you, including showing you relevant ads on other websites.