Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
01-03-2013 04:13 PM - edited 01-04-2013 08:37 AM
The app I'm trying to create supports oauth2 and since I'm really new at this I would really appreciate if someone could help me understand what I need to code or how to use the library that Kyle Fowler created.
My website needs these parameter to be sent:
I want to unserstand what is the redirect_uri I need to input. And finally how to I end up with something like that:
Example request (x-www-form-urlencoded):
POST /v3/oauth/request HTTP/1.1 Host: Content-Type: application/x-www-form-urlencoded; charset=UTF-8 X-Accept: application/x-www-form-urlencoded consumer_key=1234-abcd1234abcd1234abcd1234& redirect_uri=myapp1234:authorizationFinished
Thank you for the help.
01-03-2013 07:18 PM
On mobile devices, the easiest way of handling OAuth is by using an embedded web view. In that case, the redirect URI is just a string. Any string. It could be the name of your pet goldfish. Or a randomly generated string. As long as it doesn't occur in the normal oauth dance you're fine. You simply use it to detect when your token has been generated by handling the navigation event of the web view:
For historical reasons, the prefix oob:// (meaning out-of-band) is often used, but there is no requirement for that.