title: Flask User Management : How to make Stateless Server using better authentication ways?
body: <ul>
  <li><p>I have been reading at multiple places and it is suggested that the Web Servers should be <strong>Stateles</strong> with <strong>share nothing architecture</strong>. This helps them scale better.</p>
  </li>
  <li><p>That means each request has all the information needed to process the request.</p>
  </li>
  <li><p>This becomes tricky when you have <strong>REST</strong> endpoints that needs authentication.</p>
  </li>
  <li><p>I have been looking at ways Flask extensions do this and <a href="http://pythonhosted.org/Flask-Login/" rel="noreferrer">Flask Login</a> extension is defined as</p>
  </li>
  </ul>
  <blockquote>
  <p>Flask-Login provides user session management for Flask. It handles the
  common tasks of logging in, logging out, and <strong>remembering your users’
  sessions</strong> over extended periods of time.</p>
  </blockquote>
  <ul>
  <li>This seems like against the philosophy of building a <strong>Stateless</strong> server, isn't it?</li>
  <li>What are better ways to build a <strong>Stateless</strong> server with authentication provided via HTTP headers with Python or related python libraries?</li>
  </ul>
  <p>P.S: Apologies for not posting a programming question here, this is a design issue and I do not know how to solve it and SO seems to have right people to answer such questions. Thanks.</p>