OAuth conflicts with ANY cookie manager

Using Streamlit
,
1

UPDATE: RESOLVED → after much pain agony, here’s the solution for anyone else who pulls their hair out with this: they can co-exist if cookie controller is limited to two rerun chances to get cookie since it will never get cookie on the first rerun likely due to inner workings of session state it is establishing. If >2 reruns, do not invoke the cookie controller otherwise it will conflict with OAuth. It must go straight to OAuth logic at that point. The cookie controller cannot be a global variable but only conditionally invoked. It can never be invoked on the same rerun that OAuth might be triggered. It can be invoked on the same run as OAuth to set the cookie but only after OAuth has finished is job.

Original Problem:

I can authenticate with Google OAuth, yay…BUT, I can’t also initialize a cookie manager to save token. I’ve tried 3 different 3rd party streamlit cookie libraries and the identical problem persists on all 3 of them

  1. streamlit-cookies-controller
  2. extra_streamlit_components
  3. streamlit_cookies_manager

If any of those are initialized BEFORE OAuth executes, the script errors when OAuth runs due to some apparent dependency conflict.

Has anyone worked around this to implement OAuth while also initializing a cookie controller to persist data across sessions? I’m on 1.35.0

2

Hey,

just an idea:

I made good experience using this library to set and read cookies (prior v.1.37):

aghasemi/streamlit_js_eval: A custom Streamlit component to evaluate arbitrary Javascript expressions (github.com)

You can import the functions set_cookie and get_cookie to handle everything cookie related. However, please not that for reading the values of cookies I would recommend using the new native Streamlit feature st.context feature which was just released in v.1.37.