Application (Client and Service)

In Cloudentity, Application is defined as a Client and Service. Client can be understood either as an OAuth 2.0 Client or as a SAML Service Provider. Cloudentity exposes a SAML SSO login and metadata endpoints for SAML apps and protects their resources by enforcing the assigned policies (such as MFA requirements for users).

Services are a bit more complicated. Essentially, the whole set of services in a Cloudentity Workspace constitutes the OAuth 2.0 Resource Server. Cloudentity recognizes that such a server can expose a large number of APIs grouped into particular services, and consequently represents this in the Workspace in order to allow for more fine-grained access control.

To reflect the the application architecture, make management easier, and make it more intuitive for client application developers Cloudentity associates scopes and APIs to services.

Cloudentity also reflects microservices as services within a Workspace. These services have their own identity that is used to perform access control within distributed application. The internal microservices may not be part of the resource server as while communicating between each other they don’t use access tokens issued by the Workspace authorization server.

Add Apps

With Cloudentity, you can:

• Add client apps manually:

  • OAuth Clients

  • SAML Clients

• Add services:

  • Manually

  • By using automatical service discovery when connecting Cloudentity Authorizers to API gateways or service meshes.

• Enable developers to dynamically register their apps using OAuth DCR

• Enable developers to create applications and services using Cloudentity developer portals