Databases
StackOverflow2013
Postsdbo
POHow to manage Authentication/Authorization for user requests sent from native mobile apps calling Play2!-Scala REST services
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to manage Authentication/Authorization for user requests sent from native mobile apps calling Play2!-Scala REST services
    primarykey
    data
    text
    <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>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USkaffein
    1. USkaffein
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to manage Authentication/Authorization for user requests sent from native mobile apps calling Play2!-Scala REST services
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to manage Authentication/Authorization for user requests sent from native mobile apps calling Play2!-Scala REST services
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow to manage Authentication/Authorization for user requests sent from native mobile apps calling Play2!-Scala REST services
      1. USTaggiasco
      1. VTFavorite
    1. CONo, the Play auth module you're referring to can't be used for stateless REST authentication because yes, it uses cookies. I would suggest you look at similar questions such as http://stackoverflow.com/questions/454355/security-of-rest-authentication-schemes it's not really all that hard to implement your own. I would suggest staying away from OAuth unless you're a masochist though.
      singulars
      1. POHow to manage Authentication/Authorization for user requests sent from native mobile apps calling Play2!-Scala REST services
      1. USthatsmydoing
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload