StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18126280
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-08T12:39:45.300
FavoriteCount
0
LastActivityDate
2013-08-08T13:16:24.740
LastEditDate
2013-08-08T13:16:24.740
LastEditorUserId
261122
OwnerUserId
2664453
ParentId
14652957
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
In short, yes. You should be using the oAuth2 RFC to determine which workflow you want to use. In regards to client registration the RFC specifically states that the means through which a client registers is beyond the scope of the specification (<a href="http://tools.ietf.org/html/rfc6749#section-2" rel="nofollow">http://tools.ietf.org/html/rfc6749#section-2</a>). With that being said I can give you some insight into how I did this. My application is a mobile phone application that connects to several services running on various servers. I'm also using the <code>Resource Owner Password Credentials Grant</code>. The way I approached this was: when the application loads, the first thing it does is to check if it has an <code>oAuth2 client id</code>. If it doesn't, then it POSTS to a create client endpoint I've setted up with the meta-data I need. The endpoint validates the POST, creates the client and returns the client information. The application stores the client id and the process doesn't have to be repeated the next time. <ol> <li>Application loads;</li> <li>Application checks for oAuth2 client id;</li> <li>If there is one, the process ends;</li> <li>If there isn't, it posts to <a href="http://www.example.com/client" rel="nofollow">http://www.example.com/client</a>;</li> <li>If we get a 200, store the oAuth2 client id.</li> </ol> I could have also created the oAuth2 client when the user created an account in the application, but I wanted to make the registration process as fast as possible. Creating the client would have added some extra waiting time to the process.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFOSOAuthServerBundle Create Client
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDancrumb
UserOwnerUserId
1. USperfectGait
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POFOSOAuthServerBundle Create Client
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTApproveEditSuggestion
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.