Votre compte Red Hat vous permet d'accéder à votre profil, à vos préférences et aux services suivants en fonction de votre statut client :
Vous n'êtes pas encore inscrit ? Voici quelques bonnes raisons de le faire :
- Parcourez les articles de la base de connaissances, gérez les dossiers d'assistance et les abonnements, téléchargez des mises à jour et bien plus encore, le tout depuis un espace unique.
- Affichez la liste des utilisateurs de votre organisation et modifiez les informations, les préférences et les autorisations relatives à leur compte.
- Gérez vos certifications Red Hat, consultez l'historique de vos examens et téléchargez des logos et des documents relatifs à vos certifications.
Votre compte Red Hat vous permet d'accéder à votre profil, à vos préférences et à d'autres services en fonction de votre statut client.
Si vous utilisez un ordinateur public, déconnectez-vous de votre compte lorsque vous n'utilisez plus les services Red Hat afin de garantir votre sécurité.Déconnexion
Open banking is rapidly changing how banks make information available to their customers. It is also accelerating the adoption of application programming interface (API) management tools to industrialize the deployment of public-facing APIs. My colleague Cheryl Chiodi recently wrote about the challenges and opportunities on meeting the directive by member financial organizations (you can read it here: Open Banking - How to Leverage Open APIs for Competitive Advantage in Financial Services). My post extends that discussion, focusing specifically on API security, and in particular the importance of open identity.
Let's take a concrete example: A third-party mobile application has been built that aggregates account balances from three banks into a single view for the customer. Surely the customer does not wish to authenticate themselves three times in order to access their information.
This problem can be addressed by establishing open identity standards so that APIs can be accessed in a federated fashion. Importantly, this allows a customer to authenticate once through an established identity provider (IP). Once the customer is authenticated, relying parties (RPs), such as individual banks, are able to validate the identity without the customer logging in again.
The OpenID Foundation has created OpenID Connect, an interoperable authentication protocol, and the foundation is supported by the open banking directive Cheryl writes about in her recent post, and there is a shared objective by these two organizations to realize a secure mechanism to access bank information across API providers. It is another example where open communities and governance are allowing banks to participate in the wider Digital ecosystem.
Red Hat's 3Scale API management platform supports OpenID Connect as a security policy out of the box. This is an important capability so that a bank can allow its customers to have access to data openly and more securely.
Leading financial organizations that are seeking to maximize their reach with APIs will find that OpenID support can be a critical capability as they adapt their API platforms to support open banking.
About the author
Eric Marts is a financial services leader at Red Hat. Prior to joining Red Hat, Eric shaped solutions globally in the Retail Banking and Wealth Management business at HSBC. He has more than 20 years of professional experience across both startups and incumbents. He is particularly interested in unlocking new market opportunities and making financial services simpler and more inclusive for customers with cloud technology.