Secure, Scale, and Manage Your API Data Sharing Ecosystem

• Raidiam Connect provides Identity Access Management (IAM) for Services.
• More specifically, Connect is a developed Certificate authority that facilitates certificate based authentication of applications calling services.
• In the same way a traditional IAM service controls application / data access for users, so Raidiam Connect controls access for application / services.

It does:

• give organisations a self-service portal to register their company, their applications and their APIs.
• give organisations the opportunity to define policy related metadata (roles and scopes).
• issue transport and encryption certs which are used by client applications for the purposes of authentication, non-repudiation and data security.

It does not:

• enforce policy (this can be done via auth server or API gateway).
• handle user authentication.
• form a part of runtime access of APIs/ services (i.e. every time you call an API there is no need to call Raidiam Connect).

• They complement each other. Raidiam Connect is used to define policy and API gateways can enforce that policy. Think of it like a security guard (API Gateway) and security clearance database (Raidiam Connect).
• However, in a user-not-present communication, Raidiam can act as the auth server (for example, a Core banking system needs to talk to issuer processor on an ongoing basis).
• API gateways are effectively on prem / part of your local architecture.

If you look at bank's developer portal, you'll typically find similar elements:

1. Discovering APIs – Developers can explore what APIs are available, including information on products, data schemas, and interaction guidelines. This is essentially API definitions, documentation, and a public-facing site to showcase the APIs.
2. Sign-up, registration, and consumption – This is where Raidiam Connect comes into play.

Raidiam Connect isn't a "rip and replace" solution for a developer portal. Instead, it complements the existing content that developers use to explore API catalogues and documentation. Once developers are ready to register, sign up, declare their software application/client, and obtain credentials, that's where Raidiam Connect fits.
Beyond that, organisations will still need:

• An Authorisation Server/OpenID Provider (OP) to handle third-party provider (TPP) authorisation and authentication, which includes customer authentication and consent management. Well recognised names in the space are Ping/Forgerock & Okta
• An API Gateway to surface and secure their APIs, e. Apigee, Kong, etc.

• We expect Raidiam to fit into an intuitive user journey for Bank clients. Once developers are ready to register, sign up, declare their software application/client, and obtain credentials (even in sandbox) we’d expect a hand-off to Raidiam to complete this activity. If Bank has their own interface, they can maintain this and complete this activity via Raidiams APIs. We also have a GUI if required too.
• There is flexibility around the implementation and resultant customer journey, which we could explore in more detail if you’d like.

IAM tools (e.g. Ping, Auth0, Okta):

• IAM tools allow you to define policy for User Access. Raidiam Connect allows you to define policy for Organisation and Application access. Raidiam Connect also includes a Certificate Authority, whilst IAM tools don’t.

API Gateways (e.g. Kong, APIgee, Mulesoft):

• Raidiam Connect and API gateways are complementary. Raidiam Connect is used to define policy and API gateways can enforce that policy. Think of it like a security guard (API Gateway) and security clearance database (Raidiam Connect).
• More broadly, an API gateway is a presentation layer and provides a front to internal architecture.

Generic CA’s (e.g.AWS CM, Digicert):

• Raidiam Connect is delivered as an out-of-the-box managed service. It includes a developed directory capability (Orgs, Apps, APIs) against which certificates are issued. Raidiam Connect therefore mitigates against the need for significant complex build to implement a Certificate Authority in use cases where access is differentiated.
• Radiam connect layers the ability to define client application oauth metadata.

Raidiam Connect enables your customers to self-serve when rotating application credentials, either via an easy to use GUI or via a highly functional API. Our APIs allow our customers and their clients to implement automated credential rotation.

• authn - client_secret_basic, client_secret_post, private_key_jwt, mTLS client authentication
• authz - OAuth 2.0, FAPI parts 1&2

Raidiam Connect enables your customers to self-serve when rotating application credentials, either via an easy to use GUI or via a highly functional API. Our APIs allow our customers and their clients to implement automated credential rotation.