Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The problem that you describe with "delegated authentication" is a real one. It means that a "client application" using it's credentials has access to the whole breadth of user data. This access can be used maliciously (for example a "semi-trusted" app harvesting api data) or negligently (for example an app accidentally exposing a Direct Object Reference Vulnerability - <a href="https://www.owasp.org/index.php/Top_10_2010-A4-Insecure_Direct_Object_References" rel="nofollow">https://www.owasp.org/index.php/Top_10_2010-A4-Insecure_Direct_Object_References</a>)</p> <p>Probably the most prevalent "token based" scheme is OAuth2 (<a href="http://oauth.net/2/" rel="nofollow">http://oauth.net/2/</a>), and the precursor, OAuth, which many sites choose to continue to use.</p> <p>OAuth2 has a number of roles:</p> <ol> <li>resource owner (the user in your case) </li> <li>resource server (your api)</li> <li>client (the apps you talk about) </li> <li>authorization server (not clear who or what would fulfil this role in your case)</li> </ol> <p>The basic scheme is that the resource owner authenticates using their credentials directly with the authorization server. They are then asked if they want to grant some information (which may just be a persistent identifier, or a description of the information exposed by your api) to some client. When they accept an 'auth code' is sent to the client and they use that (combined with their own credentials) to receive an 'access token'. This access token can then be used to authenticate against the resource server (which can check it's authenticity back against the authorization server).</p> <p>Normally the way this is used is that the authorization server and the resource server are owned and managed by the same entity (for example google and facebook would fulfil this role) and then clients are independently managed.</p> <p>The scheme can also be used internally within an organisation without the "explicit grant" which can still at least confirm that a specific end-user is present before releasing any data from an api.</p>
    singulars
    1. This table or related slice is empty.
    1. POEnd user authentication for RESTful web services
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USPhil Parker
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POEnd user authentication for RESTful web services
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThis is really helpful. I considered OAuth2 but assumed that it was a poor match because I have fine-grained ACLs on the service side, and all the OAuth2 examples I've seen involve granting coarse-grained permissions (e.g., give such-and-such app permission to post on your wall).
      singulars
      1. PO
      1. USWillie Wheeler
    2. COSo the magic search term for you is 'scopes'. OAuth2 has an extensible scopes mechanism which means you can add pretty fine grained controls but it relies on you agreeing it in advance with the Authorization Server. In this case the 'grant' screen would ask if they were willing to give access to e.g. "your mother's shoe size" based on a scope of 'mothersshoesize'. The scopes that an app wants are passed to the Authorization Server when the client redirects the user.
      singulars
      1. PO
      1. USPhil Parker
    3. COCan I just have the client pass the token to the web service, and then have the web service resolve the token to a user and then apply any ACLs? I'm not really looking to give the end user the ability to grant the client app to access such-and-such data (which I think is the normal OAuth use case). Instead, the client authenticates to the service *as* the end user (e.g., by passing the token), and so the client can do whatever service allows that end user to do. Let me know if OAuth2 is still a candidate here.
      singulars
      1. PO
      1. USWillie Wheeler
 

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