Issue with generating OAuth 1.0a tokens and using the Core API's

  • 1
  • Announcement
  • Updated 4 years ago
We've recently discovered that the method we have outlined here for obtaining OAuth 1.0a tokens to use with our Core API is no longer effective. What this means is that 3rd Part Developers are currently not able to use the Core API's. 

This is a high priority issue for us, and we very much apologize for the inconvenience it causes. We will update this forum discussion with any updates.

Thanks!
Photo of Robb

Robb, Official Rep

  • 76,676 Points 50k badge 2x thumb

Posted 4 years ago

  • 1
Photo of Robb

Robb, Official Rep

  • 76,676 Points 50k badge 2x thumb
I wanted to update everyone with where we are regarding this issue:

As you know we have encountered an issue with OAuth 1.0a authentication which prevented newly registered 3rd Party Developers from accessing our API. We have determined that this issue is related to the deprecation of OAuth 1.0a support in Google AppEngine which is currently scheduled to be shut off in April 2015. Unfortunately we will not be able to restore the ability to access our API for all developers who have registered after May 20, 2014 (developers who registered before that date will still be able to authenticate until April 2015). 

We have temporarily closed the new 3rd party developer registration while we are developing the next generation of our API based on Google Cloud Endpoints which will no longer depend on OAuth 1.0a. 

Once the basic functionality is in place, we will be releasing an early preview of the new API and we encourage 3rd party developers who already have working apps that use our existing API to get back to us and tell us their needs in terms of functionality as well as any feedback they may have. Based on that we will determine the schedule for implementing the rest of the API functionality as well as requested changes (if any). Once the implementation of the new API is complete we will announce the deprecation schedule for the existing API and ask the developers of the existing apps to begin planning the migration.

Please stay tuned for more updates, and let us know if you have any questions. Thanks!
Photo of Robb

Robb, Official Rep

  • 76,676 Points 50k badge 2x thumb
Hey everybody,

I wanted to update this conversation to let you know that our new API's are almost completed, and you can find them here: https://rvacore-test.appspot.com/_ah/api/explorer. You can also check out the Github repo for the API's here: http://rise-vision.github.io/core-api/. Both repositories will update as new functionality is added.

Not all the functionality is there yet, but it is well on it's way! If you have any questions or concerns, please let us know! 

Thanks!
Photo of Tyler Balaban

Tyler Balaban

  • 344 Points 250 badge 2x thumb
Hi Robb,

I was planning on diving into the API's but with oAuth 1.0a being deprecated and soon to be unusable, what is the best way to start developing for the new oAuth implementation. Ideally, I was hoping to setup something within the next week or two.

is the core-api updated in the current RiseVision product?

Also a side question, I noticed for the old API that if you GET a presentation, the output is XML, so I wasn't entirely sure how to PUT something as I assumed it required json input.

Please advise, 
Any small code snippets  of examples are greatly appreciated.

Thanks so much for your time.
Photo of Neal

Neal

  • 61,252 Points 50k badge 2x thumb
Just wanted to update everybody that our new APIs have been recently completed.  You can check them out here.

Thanks!