 This is Jason Porter with the Red Hat developers program, and we have Sebastian Blanc with us. Thanks for being with us, Sebastian. Thank you. Now, I know your tenure at Red Hat, you've been doing a multitude of different things. I believe you started out working on Aerogear and some of our mobile initiatives. Exactly. And you also dabbled in some of the IoT space as well. A little bit, not officially, but it's not ten years, five years. No, ten years. You're your term here at Red Hat. Oh, yeah. Not ten years. Ten years. Ten years, sorry. It's all good. It's my French... No, it's okay. We won't hold it against you. It's all good. And now I believe you're working on security and key clove, right? Exactly. I joined the key clove team a few months ago. Okay. And I'm really happy about it because it's an amazing project, fast growing community, and a lot of things to do. And people love it because, yeah, security is not the most enjoying part of an application, but it's critical. Sure. And if you show people that you can make security easy and almost fun, well, they really like it. And so I really enjoy working on this project. I travel a lot in conferences to advocate for this and just showing people how in ten minutes you can secure your app and add complete identity management to your app. And while respecting modern protocols like OpenID and stuff like that, integrating social login, you can even have user federation with LDAP. So for instance, if you bring key clove to your company but you already have an LDAP directory with all your users there and you still want to use them, well, key clove can make the bridge. Okay. I could use something like Active Directory or something like that. Okay. Very good. And that can make the migration. If you want to move away and do a full deploy key clove, but you can do a soft migration by in the beginning doing user federation with your LDAP users. Okay. And then slowly you can, yeah. Very good. I know a lot of people looking at security and whatnot and we've talked a lot about user identity and identity management with key clove, right? LDAP or various other data stores for the identity of the user. How else can I use key clove? Can I use it to say secure my application at a method level or at a class level? How fine-grained can I get with key clove? Okay. Key clove has different options for security. The basic part is the authentication. So, here we are not speaking about authorization yet, but that's the first part, the first layer. So, we authenticate the user and once you have that, well, we have a whole authorization layer and where you can do attribute-based authorization. Okay. Very interesting. You can integrate your business engine rule like drills. You can integrate drills with key clove and, well, make authorization decisions based on your engine rule. Excellent. But even without using our authorization layer, you can keep pretty basic authorization stuff just by using role-based access. That's pretty easy. Just, for instance, if you are securing a Java EE app in your web.xml, you specify security constraints and you can say, well, for this URL, I just want users with the role admin to be able to access it. So, if you don't want to dive into the authorization layer, which can be quite complicated, you cannot keep almost everything without touching that. Oh, very good. Very good. I know I'm going to do a little bit of history real quick. Some of our viewers may be familiar with a previous product or project that we had called Pickett Link. So, what's the history between Pickett Link and key clove? Okay. So, Pickett Link was one of the first security projects I had read it. But it was part of, it was integrated in the application server itself. So, if you wanted to use Pickett Link, you had to install it on your application server and once you deploy another application server, you had to install Pickett Link there again. And that's not necessarily the case with key clove. Key clove, and the key point of key clove is having a single key clove instance that can secure multiple apps. Excellent. Very good. So, what's the history of delegating your security? The security is not the matter, it's not the core of your business. So, you delegate all this to an external server, which is key clove. And so, but we kept a lot of Pickett Link, Pickett Link for instance, at the whole authorization layer. We took that code and integrated it in key clove. Okay. And there's Pedro who was on the Pickett Link, which is now part of the key clove team. Okay, very good. Very good. So, if I was using Pickett Link at some point in time, the migration step is to move to key clove. Exactly. Yes. Very good. And key clove also, for those interested in integrating with key clove, key clove also has a rest endpoint that I can get to and I can secure things like a mobile application, for example, using key clove via a rest call, right? Exactly. So, with key clove you can secure everything. So, going from a frontend app, being a web app, or a mobile native app, or an hybrid app, you can secure that. And you can secure whatever backend application you want, microservices, it's all based on rest calls. And as long as you pass the authorization token in your header, and that you integrate the key clove adapter, so we have the key clove server. And then for each application, you need to install a small library, an adapter, that can communicate with key clove, that can verify your token, and stuff like that. Is that a JavaScript adapter? Java? What do we have? So, we have a whole set of adapters. First, we have the Java adapters. So, we have the Wildfly EAP adapter for the application server. We have a Tomcat adapter, a Jetty adapter. We have a Spring Boot adapter. We even have a Spring Security adapter. So, if you are using Spring Security, for instance, and you don't want to change too much your code base, you still want to use the APIs of Spring Security, you can do that, and at the same time integrate with key clove. So, you keep doing the same thing. It's just like swapping out the back end. Exactly, exactly. And then we have a Node.js adapter for your Node.js app. Oh, very nice. And then, well, for the front end, we have a JavaScript library. You will be using this library when you secure your Angular app, for instance. Then you just have to install this key clove JavaScript library, and that's it. And from the community, we have a .NET adapter and even a C-sharp, and I think a C++ adapter. That's interesting. Yes, and while we are waiting, we cannot offer all the adapters. For instance, we would like to have a Go adapter, but we don't have the knowledge inside the team. So, it will be really nice if from the community someone could contribute to a Go adapter, for instance. So, if any of you watching out there are big Go people, then we need some help on the key clove team getting going. Exactly. And the same stands for PHP. We have a lot of PHP developers asking for us if we have a PHP adapter. And again, we don't really have this knowledge inside the team. So, again, if someone from the community wants to contribute with a PHP adapter, that will be wonderful. Oh, very good, very good. One last question. So, we've been hearing a lot about OpenShift recently. How can I leverage key clove with OpenShift? Well, key clove is available on OpenShift. So, it will be... So, I don't know how far we are, but in the new version of OpenShift, OpenShift V3, there will be a card rich. I don't know if you still would say card riches. I'm not familiar with all the terminology. Okay, yeah, that was the term for OpenShift V3. But, yeah, with the new OpenShift, one of the first products that will be available will be key clove. Excellent, very good. All right, that'll wrap us up. And thank you, Sebastien, for coming. And just, I'll help you plug real quick. So, you've got a conference coming up pretty seen over in France, right? Exactly. So, next week there's Riviera Dev. That's a conference that I'm organizing with some other Red Hat guys, Defany Pardo from the Salem team. And, yeah, it's a really nice conference on the beach. Not so far from there. Sounds like a good conference. Yes, and this year we have 400 attendees. So, we're really happy. We're a small conference, but growing pretty fast. Very good, very good. All right, thank you so much. Thank you.