pysepal.solara.dev_auth#
Local-development login for pysepal Solara apps.
PYSEPAL_DEV_AUTH exists so a developer can run an app against a real SEPAL
instance from a laptop, where no SEPAL proxy injects headers. It is a single
process-wide identity by design. A connection carrying validated SEPAL headers
never uses it for its own identity – real headers demote the plan for that
connection (see pysepal.solara._topology.resolve_session_plan()) – but
the shared session it builds is still reachable by scope id, since solara’s
kernel id is client-supplied. Not the demotion rule alone, but four explicit
reserved-scope guards keep another connection from reading or writing it:
pysepal.solara.session_manager.SessionManager._require_connection_session()
(get_gee_interface/get_drive_interface), the equivalent check at the
top of _create_connection_session, get_sepal_client’s own inline
check, and get_session_info’s: it refuses a caller-supplied
PROCESS_SCOPE the same way, while
sessions_overview()
still enumerates it internally for admin/debug UI, since a scope pulled
from the registry’s own keys was never client-supplied.
Functions
Log in once for the whole process with the developer credentials. |