Checklist
Summary
Dear Streamlit Team,
I recently experienced an issue using the st.login function with MS Entra as identifiy provider:
A user could not login, although the SSO was successful and a auth code was returned from the provider.
We noticed that the issue was that the st_user cookie could not be set.
Taking a closer look we figured that the cookie size was above the browser limit (somewhat 4 kb), hence no cookie could be set and the st.login was unsuccessful.
We notices that the was member of > 50 AD Groups which all belonged to that app, which are all stored in the cookie causing the exceeding size.
From my perspective there should at least be a warning, or error message, if cookie size becomes too large.
Thank you,
Jonathan
Reproducible Code Example
Steps To Reproduce
No response
Expected Behavior
No response
Current Behavior
No response
Is this a regression?
Debug info
- Streamlit version:
- Python version:
- Operating System:
- Browser:
Additional Information
No response
Checklist
Summary
Dear Streamlit Team,
I recently experienced an issue using the st.login function with MS Entra as identifiy provider:
A user could not login, although the SSO was successful and a auth code was returned from the provider.
We noticed that the issue was that the st_user cookie could not be set.
Taking a closer look we figured that the cookie size was above the browser limit (somewhat 4 kb), hence no cookie could be set and the st.login was unsuccessful.
We notices that the was member of > 50 AD Groups which all belonged to that app, which are all stored in the cookie causing the exceeding size.
From my perspective there should at least be a warning, or error message, if cookie size becomes too large.
Thank you,
Jonathan
Reproducible Code Example
Steps To Reproduce
No response
Expected Behavior
No response
Current Behavior
No response
Is this a regression?
Debug info
Additional Information
No response