{"id":3514,"date":"2018-10-02T11:07:43","date_gmt":"2018-10-02T15:07:43","guid":{"rendered":"https:\/\/solutionsreview.com\/identity-management\/?p=3514"},"modified":"2018-10-02T11:07:43","modified_gmt":"2018-10-02T15:07:43","slug":"understanding-api-protection-with-oauth-2-0-with-ubisecure","status":"publish","type":"post","link":"https:\/\/solutionsreview.com\/identity-management\/understanding-api-protection-with-oauth-2-0-with-ubisecure\/","title":{"rendered":"Understanding API Protection with OAuth 2.0 (with Ubisecure)"},"content":{"rendered":"

\"Understanding<\/p>\n

Application Programming Interfaces\u2014better known as APIs<\/a>\u2014are the software intermediaries allowing communications between applications. For enterprises, APIs are essential to ensuring appropriate security, security auditing, and gatekeeper capabilities on enterprise networks. Yet simultaneously, APIs can appear as a complex and daunting feature to outside observers. \u00a0\u00a0\u00a0<\/span><\/p>\n

\t\t\t

\"Download<\/a><\/p>\n<\/div>\n\t\t<\/div><\/div><\/p>\n

European customer identity and access management (CIAM) solution provider Ubisecure works to dispel this complexity in their \u201cAPI Protection with OAuth 2.0: Security, Identity & Authorization for the API Economy<\/a>\u201d white paper. In it, Ubisecure also explores API protection in relation to identity. \u00a0<\/span><\/p>\n

Here are some of the key findings from the API Protection with OAuth 2.0 white paper by Ubisecure<\/a>:<\/span><\/p>\n

A Word of Introduction <\/b><\/h3>\n

To function optimally and securely, APIs need to know who is accessing their standardized communications. Throughout the years, APIs have used a variety of tools and capabilities to pass authorization and authentication data. These range from asking for additional username\/password parameters, to utilizing API keys, to using an OAuth 2.0 based token support. <\/span><\/p>\n

Often, these capabilities depend on the enterprise\u2019s architecture: \u00a0<\/span><\/p>\n