OAUTH and secure content

[Steve]

I have been able to successfully migrate to the graphql API for unsecured content, and I am gaining an appreciation for the interface, but when I try to access secured data with valid client credentials, I get an 'You must be authenticated to perform the requested operation' error message.  Just to be clear, these credentials worked before and after the test on the old API.  Do I need to authorize a new app to use the new API or can I use an existing app?  Is there some other special process to get OAUTH working under the new API?

[mfab]

Hi Steve,

Thanks for sharing your experience with working Kiva's graphql API.  Kiva engineering is also upgrading it's authentication procedure for applications. New credentials will be needed to access secure content, and we will make an announcement to the Kiva Build community when the new procedure is ready for release. 

We appreciate your efforts in working with the Kiva API and your patience as we move forward with the stack upgrade!

[Sam T]

Just wondering if there is any update on this?  Will the rest api stay up until this is available?

(I am using my loans, my balance and my teams in my app)

[mfab]

Hi Sam,

 

Authentication for graphql access is on the current engineering roadmap. Making secure app authentication for the new endpoint available to the build community is currently considered a todo task before full deprecation of the rest api is complete. 

Thanks for helping extend Kiva's reach with your app!

[Daniel Shafer]

Is there a projected date for the graphql authentication to be done?

[mfab]

Hi Daniel,

Kiva's plan is to complete full migration to graphql and deprecrate the REST API by the end of 2020, otherwise no further update than that. 

Hope this information helps!

[nimro...@lynxsolutions.eu]

Hey guys,

Any update on the roadmap for authentication with the GraphQL API?