o &zh)ã@sJddlZddlmZmZmZddlmZddlmZGdd„dej ƒZ dS)éN)ÚAnyÚDictÚOptional)Ú SessionBase)Ú HttpRequestc@sŠeZdZdedeefdd„Zdedeeeeffdd„Z dedeefdd„Z e j dedefd d „ƒZ e j d edeefd d „ƒZdS)ÚAbstractTokenStrategyÚrequestÚreturncCs|j d¡}|S)z4 Returns the session token, if any. zx-session-token)ÚheadersÚget)ÚselfrÚtoken©rúW/var/www/html/kangema/venv/lib/python3.10/site-packages/allauth/headless/tokens/base.pyÚget_session_token s z'AbstractTokenStrategy.get_session_tokencCs| |¡}|s dSd|iS)zã After authenticating, this method is called to create the access token response payload, exposing the access token and possibly other information such as a ``refresh_token`` and ``expires_in``. NÚ access_token)Úcreate_access_token)r rÚatrrrÚcreate_access_token_payloads z1AbstractTokenStrategy.create_access_token_payloadcCódS)aŒCreate an access token. While session tokens are required to handle the authentication process, depending on your requirements, a different type of token may be needed once authenticated. For example, your app likely needs access to other APIs as well. These APIs may even be implemented using different technologies, in which case having a stateless token, possibly a JWT encoding the user ID, might be a good fit. We make no assumptions in this regard. If you need access tokens, you will have to implement a token strategy that returns an access token here. Nr©r rrrrrsz)AbstractTokenStrategy.create_access_tokencCr)zC Create a session token for the `request.session`. NrrrrrÚcreate_session_token/sz*AbstractTokenStrategy.create_session_tokenÚ session_tokencCr)zˆ Looks up the Django session given the session token. Returns `None` if the session does not / no longer exist. Nr)r rrrrÚlookup_session6sz$AbstractTokenStrategy.lookup_sessionN)Ú__name__Ú __module__Ú __qualname__rrÚstrrrrrrÚabcÚabstractmethodrrrrrrrrsÿ þ r) rÚtypingrrrÚ%django.contrib.sessions.backends.baserÚ django.httprÚABCrrrrrÚs