Channels ▼
RSS

Open Source

Apigee's Antidote To Developer OAuth "Pain"


API specialist Apigee has this week launched OAuth API to address the "pain and complexity" that the company says developers experience when implementing OAuth (Open Authorization) across several APIs. Free in its current beta form, the new tool is intended for developers building social apps with the Salesforce REST, Chatter, LinkedIn, and Twitter APIs.

Apigee explains that OAuth is an open standard that allows users to share private resources stored on one site, with those on another site, without having to expose personal credentials such as username and password. The issue at hand here (according to Apigee) is that while OAuth can theoretically make the authentication process for mobile and native apps essentially "future proof," using OAuth can be a complex and cumbersome process for developers.

"OAuth is great for consumers, but can be painful for developers. By providing a single API for using OAuth across many different APIs, this new product makes OAuth relatively pain free," said Chet Kapoor, CEO, Apigee. "Mobile, social, and cloud platforms are the new strategic channel and business imperative in the post-browser web. With developer tools such as Apigee OAuth API, Apigee continues to make it easier and faster for developers to unleash the power of APIs for building apps."

The developer challenge here is no simple matter: There is a common need to leverage and then authenticate multiple social and enterprise APIs — Twitter, LinkedIn, Salesforce REST, Chatter, and more as Apigee adds them — and from this point then be able to use native code libraries so that apps can be built faster. It is this task that Apigee OAuth sets out to conquer.

In line with this central product release, Apigee has also announced two new interactive API Consoles, so that developers can explore, learn, and test APIs more easily. The company also provides an enterprise API management platform for developers to ease (yet more) pain when dealing with multi-channel strategies.

The core message here is the option for enterprises to reduce the complexity of providing APIs, driving developer adoption, analyzing and understanding API usage, and easily scaling as customers' API channels grow.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video