Do not know this level of problem solving higher I do not have enough for it
2010/11/3 Jørn Wildt <[email protected]> > I am working with a setup where a Windows WPF application opens up a > browser window to let the end-user authorize himself at some OAuth > endpoint. At the end of the authorization the OAuth server responds > with a redirect URL as described in section 3.1 of the OAuth 2 spec > (http://tools.ietf.org/html/draft-ietf-oauth-v2-10). > > The point of doing this, instead of getting username/password from WPF > and sending it to the OAuth server, is that we don't exactly know how > the end-user is going to authenticate himself at the OAuth end-point. > We simply let the OAuth server take care of it. > > Unfortunately this also means that we don't even know who the user is! > The OAuth response contains code/access_token + expires_in + scope + > state. None of this can be related to the end-user from the desktop > application's point of view. > > The OAuth secured system has a REST API where we can get a personal > ATOM newsfeed at the url http://somehost/<enduserid>/newsfeed. But we > have no way of knowing what to use as <enduserid>. > > There are lots of ways for us to solve this, for instance by sending > the username in the OAuth redirect response. But none of the methods > adheres to any standard. > > Does anyone know if there is some part of the standard that solves > this problem? > > Thanks, Jørn Wildt > > -- > You received this message because you are subscribed to the Google Groups > "OAuth" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected] <oauth%[email protected]>. > For more options, visit this group at > http://groups.google.com/group/oauth?hl=en. > > -- Fro :Alwi Oemar AS Http://www.oneasse.com [email protected] [email protected] -- You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/oauth?hl=en.
