User ID or other Account info?

[Richard Luck]

Is it possible to get any identifying user information back from the `/oauth/access_token` endpoint?  Ideally, I'd like to know "which" Rhapsody user is authenticated into the app I'm building - and to know when they return.  Right now there does not seem to be a way to uniquely identify the authenticated user.

Thanks for the feedback,

Rich

[David Poncelow]

Richard,

The best bet is by using your redirect_uri parameter on the /authorize endpoint- if you pass parameters there, they will be retained when you get the redirect back.  So if you have a user id in your system, you can pass it and get it back when you receive your auth code.

For example, if your registered endpoint in the developer portal is http://foo.bar, then when you call /authorize, call it as http://foo.bar?id=bob, and that’s the URL that will be redirected to after authorization.  Additional path information is fine too- you should also be able to specify http://foo.bar/users/bob as the redirect_uri.

David

--
You received this message because you are subscribed to the Google Groups "Rhapsody API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rhapsody-api...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Richard Luck]

David,

I'll follow this pattern for now.  Ideally, I'd like to use Rhapsody oAuth as the primary authentication mechanism so there is no need to integrate another friction point into the app. 

Is there a feature on the roadmap to return unique user information upon successful authentication?  If not, how do I submit that request?

Rich

[Tor Langballe]

I'm trying the append paramter to redirect url approch, and I'm getting the redirect with code appended with ANOTHER "?". 

I.e: redirect_uld?myinfo=xxx?code=YYYY

It's not smart enough to see parameters have already started.

so using ? in the redirect url isn't a great solution. Perhaps appending path is better.

tor