title: How to manage Authentication/Authorization for user requests sent from native mobile apps calling Play2!-Scala REST services
body: <p>I have been digging into Play2!Scala documentation about possible ways of implementing authentication/authorization for user requests and I must say that I am a little bit lost.
  I would like to know more about how requests sent from mobiles devices are authenticated/authorized on a Play2!Scala-backed REST-service.</p>
  
  <p>First of all, it seems that there are many auth-modules for Play2/scala : e.g <a href="https://github.com/t2v/play20-auth">t2v's Play20-auth</a>. But the thing is, these solutions are based on storing cookies on the client-side. Is that Right ? Which makes sense in a <strong>pure web perspective</strong> : requests are sent from a browser, the server can store cookies on the client etc.</p>
  
  <p>Now, what if I have a native mobile application (on IOS or Android) and I am just calling a REST service backed by a Play2!Scala app. In this case, I am not using a browser, so the server can not store cookies on the client app.</p>
  
  <p>Can I still use modules like <a href="https://github.com/t2v/play20-auth">t2v's Play20-auth</a> for authorization/authentication ?</p>
  
  <p>What are the best practices for dealing with this kind of thing ?</p>
  
  <p>Any help would really be appreciated,
  Thanks in advance,</p>