## Keeping Your APIs Secure for Multiple User Types
In an enterprise API management platform, applications acting on behalf of customers and consumers, internal business units and employees, and external organizations and their employees, are likely functioning as both API providers and consumers.

In many cases, applications acting at the behest of consumers will also represent the largest group of API consumers. As a result, these systems must be able to securely support multiple user communities while allowing for scalability, availability, and reliability—without increasing complexity.  
  
Read the full post [here](https://apigee.com/about/blog/developer/keeping-your-apis-secure-multiple-user-types).

## Design Principles for Seamless User Authentication
This post continues the discussion from the previous article regarding authentication across multiple user communities. It briefly explores identity design pattern recommendations for these situations.

Read the full post [here](https://apigee.com/about/blog/developer/design-principles-seamless-user-authentication).

## An Alternative to Delegated Access in the Enterprise
Extending OAuth2 and OpenID Connect as the enterprise standard for API security

[OAuth2](https://www.linkedin.com/pulse/saml2-vs-jwt-understanding-oauth2-robert-broeckelmann) and [OpenID Connect](https://www.linkedin.com/pulse/understanding-openid-connect-series-robert-broeckelmann) (OIDC) have their origins in the concept of delegated access (think three-legged OAuth). These protocols are designed around the notion that the resource owner is an end-user. For the enterprise, however, the business may own the data and have control over when to grant access. This article explores how an enterprise IT organization may go about defining the policies around such access.

Read the full post [here](https://apigee.com/about/blog/developer/alternative-delegated-access-enterprise).

## Identity Propagation in an API Gateway Architecture
As enterprises continue to broaden their usage of APIs, the need to increase security around those APIs also grows. One way to fortify security and strengthen auditing and authentication is the transmission of an authenticated user’s security context from the front end of a request pipeline, past the API gateway, and through to the back-end implementation of an API or service.

End-to-end transmission of an authenticated user’s security context aids API-based systems by improving overall security, cancelling out the use of generic (privileged) accounts, administering a protected audit mechanism (of traffic traversing the system), and backing cutting-edge authentication use cases.

Read the full post [here](https://apigee.com/about/blog/developer/identity-propagation-api-gateway-architecture).

For all things API, visit [Apigee.com](http://apigee.com).



Exploring API Security with Apigee

In many cases, applications acting at the behest of consumers will also represent the largest group of API consumers.

Exploring API Security with Apigee

Exploring API Security with Apigee

Read the Blog