Databases
StackOverflow2013
Postsdbo
POSecurity with Play! from Outside Application
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSecurity with Play! from Outside Application
    primarykey
    data
    text
    <p>I am working on writing a private REST API with Play! that I will make calls to from a mobile application and I am confused about how to keep it secure. </p> <p>When working through the Yet Another Blog Engine example in Play!'s documentation, I worked through their <a href="http://www.playframework.com/documentation/1.2.2/guide8" rel="nofollow noreferrer">authentication example</a>, and it deals with logging in through a browser. From what I understand about Play!'s Secure module, it helps with browser sessions. Additionally, every StackOverflow question I have seen has been involved with an administration module on the web and the questions have been pertaining to sessions as well.</p> <p><a href="https://stackoverflow.com/questions/8731624/does-the-play-framework-have-any-built-in-mechanism-to-prevent-session-hijackin">Does the Play! framework have any built in mechanism to prevent session hijacking?</a></p> <p><a href="https://stackoverflow.com/questions/7415030/enforce-https-routing-for-login-with-play-framework">Enforce Https routing for login with play framework</a></p> <p>My current understanding of how the security should work:</p> <ul> <li>The mobile app "logs in" to the web app and obtains some kind of token</li> <li>With each subsequent call the token is appended to the end of the API call</li> <li>If the mobile user "logs out" or the token expires, the web app removes the token</li> <li>Every API call uses HTTPS in order to maintain security</li> </ul> <p>Is it possible for me to make an HTTP request from the mobile application to the web application I create using Play! Framework while keeping it secure?</p> <p>Am I approaching the whole situation incorrectly?</p> <p>This is the first Play! app I have created and this is the first time I have used Heroku. I am not too far in that I would be opposed to switching to something else if it were significantly easier/more efficient/better suited to solve this problem.</p> <p><strong>EDIT:</strong> Also, in Play!'s YABE tutorial, it seems like they check the password in plain text. Just from a general standpoint, how is that not a security issue?</p> <p><strong>EDIT 2:</strong> I have looked over OAuth provider information and it seems to solve the problem. My only apprehension with it is that v2.0 has known security flaws and v1.0 seems complicated to implement for a situation where all I need is a secure connection between a mobile app and a web app. If I were to make every call require SSL, could I make each Play method just take username and password as parameters and disregard OAuth completely?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USeliot
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSecurity with Play! from Outside Application
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSecurity with Play! from Outside Application
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSecurity with Play! from Outside Application
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO"in Play!'s YABE tutorial, it seems like they check the password in plain text" - depends what you mean by plain text. If it's over HTTPS, it's not a problem to send the password in a request. If they're storing the password in the database in plain text, that's bad. Shame when tutorials completely ignore basic security "for simplicity".
      singulars
      1. POSecurity with Play! from Outside Application
      1. USNick
    2. COFrom the links you've used it looks like you're using Play 1.x. Any reason you're not going with 2.x?
      singulars
      1. POSecurity with Play! from Outside Application
      1. USNick
    3. COHeroku by default uses Play 1.2.4. I don't know of a reason to upgrade it as of right now and time is the most important thing in regards to the mobile app.
      singulars
      1. POSecurity with Play! from Outside Application
      1. USeliot
 

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