What are the advantages of using pyramid_beaker instead of just using something like AuthTktAuthenticationPolicy for session authentication?
What are the advantages of using pyramid_beaker instead of just using something like AuthTktAuthenticationPolicy
Share
AuthTktAuthenticationPolicyonly issues encrypted authentication cookies, and are not, in a technical sense, tied to sessions. You can only use this to identify, securely, that a user is still the same entity that logged in during an earlier HTTP connection. The cookie contains all the information needed to re-identify the user on every HTTP request.AuthTktAuthenticationPolicycookies are compatible with themod_auth_tktApache module.A
pyramid_beakersession on the other hand, uses a cookie to tie a returning browser connection to some persistent server-side information. Using such a session allows your application to associate arbitrary data with a website visitor, that is not stored in the browser.See Webserver Session management on Wikipedia