Buckets:
AnonymousSpottedToad/candidate_bucket / preliminary /mappings /python /session_based_access_control /kinde-oss_kinde-python-sdk.json
| { | |
| "role_mappings": [ | |
| { | |
| "role": "Subject", | |
| "status": "missing", | |
| "symbol": "", | |
| "file": "", | |
| "lines": "", | |
| "notes": "The caller of the SDK-registered /user route (kinde_flask/framework/flask_framework.py:282) is a browser outside the repo; no in-repo client sends the session cookie. Tests and examples were not counted." | |
| }, | |
| { | |
| "role": "Authentication enforcer", | |
| "status": "present", | |
| "symbol": "get_user", | |
| "file": "kinde_flask/framework/flask_framework.py", | |
| "lines": "282", | |
| "notes": "Route handler for /user, registered by FlaskFramework._register_kinde_routes (called at flask_framework.py:96). It calls self._oauth.is_authenticated() at line 285 and redirects to login when that fails, so the handler itself is the enforcer. The session cookie resolves server-side through Flask-Session (SESSION_TYPE defaults to filesystem; Session(self.app) at line 63)." | |
| }, | |
| { | |
| "role": "Verifier", | |
| "status": "present", | |
| "symbol": "is_authenticated", | |
| "file": "kinde_sdk/auth/user_session.py", | |
| "lines": "130", | |
| "notes": "Reached from get_user (flask_framework.py:285) via OAuth.is_authenticated (kinde_sdk/auth/oauth.py:152), which reads user_id from the server-side session (FlaskFramework.get_user_id, flask_framework.py:127) and delegates at oauth.py:169. UserSession.is_authenticated returns False unless a session entry exists for user_id and holds a valid access token (refreshed if needed)." | |
| }, | |
| { | |
| "role": "Session manager", | |
| "status": "present", | |
| "symbol": "get_token_manager", | |
| "file": "kinde_sdk/auth/user_session.py", | |
| "lines": "119", | |
| "notes": "Called by UserSession.is_authenticated (user_session.py:132). It looks up the user's open session in the in-memory user_sessions dict and falls back to _load_from_storage (line 66), which reads StorageManager backed by the Flask-Session server-side store. Sessions are created by set_user_data (line 13) during the /callback handler." | |
| }, | |
| { | |
| "role": "Authorisation enforcer", | |
| "status": "missing", | |
| "symbol": "", | |
| "file": "", | |
| "lines": "", | |
| "notes": "No in-repo code on the /user path (or any SDK route) blocks a request based on permissions or roles. The SDK only exposes query helpers: get_permission (kinde_sdk/auth/permissions.py:9), get_role (kinde_sdk/auth/roles.py:9) and has_permission/has_role (kinde_sdk/core/helpers.py:398/485). None is wired as a guard, and the Flask example app does not use them either." | |
| }, | |
| { | |
| "role": "Decider", | |
| "status": "missing", | |
| "symbol": "", | |
| "file": "", | |
| "lines": "", | |
| "notes": "No authorisation enforcer exists, so no decider is reached. get_permission (kinde_sdk/auth/permissions.py:9) and has_permission (kinde_sdk/core/helpers.py:398) can evaluate permission claims, but they are off-path library helpers for the integrating app." | |
| }, | |
| { | |
| "role": "Policy provider", | |
| "status": "missing", | |
| "symbol": "", | |
| "file": "", | |
| "lines": "", | |
| "notes": "Not reached on the traced path. Permissions come from token claims or the Kinde account API (PermissionsApi in permissions.py:108-114, off-path); the policy itself lives in the external Kinde service." | |
| }, | |
| { | |
| "role": "System", | |
| "status": "missing", | |
| "symbol": "", | |
| "file": "", | |
| "lines": "", | |
| "notes": "Rule 7 (library/SDK repo): the only action behind the enforcer is the SDK's own /user helper route, whose handler get_user (kinde_flask/framework/flask_framework.py:289) calls OAuth.get_user_info (kinde_sdk/auth/oauth.py:171) to return user details. That is an SDK auth utility, not a protected business handler, and no in-repo app business handler is wired to the same enforcer." | |
| } | |
| ] | |
| } | |
Xet Storage Details
- Size:
- 3.83 kB
- Xet hash:
- fd4bdd6275d73d5e271aa28eac16e3d54b36544dad0d8cc886c7e315c359361f
·
Xet efficiently stores files, intelligently splitting them into unique chunks and accelerating uploads and downloads. More info.