<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Keycloak on Nicolas Massé</title><link>https://www.itix.fr/opensource/keycloak/</link><description>Recent content in Keycloak on Nicolas Massé</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 07 Jun 2021 00:00:00 +0200</lastBuildDate><atom:link href="https://www.itix.fr/opensource/keycloak/index.xml" rel="self" type="application/rss+xml"/><item><title>How to size your projects for Red Hat's single sign-on technology</title><link>https://www.itix.fr/writing/how-size-your-projects-red-hats-single-sign-technology/</link><pubDate>Mon, 07 Jun 2021 00:00:00 +0200</pubDate><guid>https://www.itix.fr/writing/how-size-your-projects-red-hats-single-sign-technology/</guid><description>Red Hat&amp;rsquo;s single sign-on (SSO) technology is an identity and access management tool included in the Red Hat Middleware Core Services Collection that&amp;rsquo;s based on the well-known Keycloak open source project. As with other Red Hat products, users have to acquire subscriptions, which are priced according to the number of cores or vCPU used to deploy the product.
This presents an interesting problem for pre-sales engineers like me. To help my customers acquire the correct number of subscriptions, I need to sketch the target architecture and count how many cores they need.</description></item><item><title>Configure Red Hat SSO for 3scale using the CLI!</title><link>https://www.itix.fr/blog/configure-redhat-sso-3scale-cli/</link><pubDate>Wed, 08 Apr 2020 00:00:00 +0200</pubDate><guid>https://www.itix.fr/blog/configure-redhat-sso-3scale-cli/</guid><description>&lt;p>&lt;a href="https://3scale.github.io/">3scale API Management&lt;/a> can be used in conjunction with &lt;a href="https://access.redhat.com/products/red-hat-single-sign-on">Red Hat SSO&lt;/a> / &lt;a href="https://www.keycloak.org/">Keycloak&lt;/a> to secure APIs managed by 3scale using the OpenID Connect protocol.&lt;/p>
&lt;p>The &lt;a href="https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.8/html/administering_the_api_gateway/openid-connect#configure_red_hat_single_sign_on">official documentation&lt;/a> describes the steps to configure Red Hat SSO / Keycloak but it uses the Graphical User Interface, which can be tedious if you have multiple environments to configure. Let&amp;rsquo;s configure Red Hat SSO for 3scale using the CLI!&lt;/p></description></item><item><title>Secure your Raspberry PI with Keycloak Gatekeeper on OpenWRT</title><link>https://www.itix.fr/blog/secure-raspberry-pi-keycloak-gatekeeper/</link><pubDate>Sat, 28 Mar 2020 00:00:00 +0200</pubDate><guid>https://www.itix.fr/blog/secure-raspberry-pi-keycloak-gatekeeper/</guid><description>&lt;p>In the article &amp;ldquo;&lt;a href="../nginx-with-tls-on-openwrt/">Nginx with TLS on OpenWRT&lt;/a>&amp;rdquo;, I explained how to install nginx on a Raspberry PI running OpenWRT for hosting web applications.
Some of the web applications that I installed on my Raspberry PI do not feature any authentication mechanism at all.
No authentication means that anybody on the internet could reach those applications and play with them.
This article explains how to secure applications running on a Raspberry PI with &lt;a href="https://github.com/keycloak/keycloak-gatekeeper">Keycloak Gatekeeper&lt;/a>.&lt;/p></description></item><item><title>Secure a Quarkus API with Keycloak</title><link>https://www.itix.fr/blog/secure-quarkus-api-with-keycloak/</link><pubDate>Tue, 17 Mar 2020 00:00:00 +0200</pubDate><guid>https://www.itix.fr/blog/secure-quarkus-api-with-keycloak/</guid><description>&lt;p>&lt;a href="https://quarkus.io/">Quarkus&lt;/a> is a Java stack that is Kubernetes native, lightweight and fast.
Quarkus can be used for any type of backend development, including API-enabled backends.
&lt;a href="https://www.keycloak.org/">Keycloak&lt;/a> is an open source Single Sign On solution that can be used to secure APIs.&lt;/p>
&lt;p>In this article, I&amp;rsquo;m describing how to secure a Quarkus API with Keycloak using JWT tokens.&lt;/p></description></item><item><title>Running Red Hat SSO outside of OpenShift</title><link>https://www.itix.fr/blog/running-redhat-sso-outside-openshift/</link><pubDate>Thu, 10 Oct 2019 00:00:00 +0200</pubDate><guid>https://www.itix.fr/blog/running-redhat-sso-outside-openshift/</guid><description>&lt;p>In an article named &lt;a href="https://developers.redhat.com/blog/2019/02/07/red-hat-single-sign-on-give-it-a-try-for-no-cost/">Red Hat Single Sign-On: Give it a try for no cost!&lt;/a>, I explained how to deploy Red Hat SSO very easily in any OpenShift cluster.&lt;/p>
&lt;p>As pointed by a reader in a comment, as widespread OpenShift can be, not everyone has access to a running OpenShift cluster. So, here is how to run Red Hat SSO outside of OpenShift: using only plain Docker commands.&lt;/p></description></item><item><title>Red Hat Single Sign-On: Give it a try for no cost!</title><link>https://www.itix.fr/writing/red-hat-single-sign-on-give-it-a-try-for-no-cost/</link><pubDate>Thu, 07 Feb 2019 00:00:00 +0200</pubDate><guid>https://www.itix.fr/writing/red-hat-single-sign-on-give-it-a-try-for-no-cost/</guid><description>In a software world where each day is more hostile than the previous one, security matters and developers are coping with more and more non-functional requirements about security. The most common ones are the “OWASP Top 10”: the ten security risks that every developer should know. There are many more security risks you should care about, but those ten risks are the ones having the most impact on the security of your software.</description></item><item><title>Using a public certificate with Red Hat Single Sign-On/Keycloak</title><link>https://www.itix.fr/writing/using-a-public-certificate-with-red-hat-single-sign-on-keycloak/</link><pubDate>Wed, 06 Feb 2019 00:00:00 +0200</pubDate><guid>https://www.itix.fr/writing/using-a-public-certificate-with-red-hat-single-sign-on-keycloak/</guid><description>When deploying Red Hat Single Sign-On/Keycloak for a test or a proof of concept, most users will choose to use a self-signed certificate as explained in the official documentation.
The setup instructions are straightforward, but this self-signed certificate will trigger certificate error messages in your web browser and can also prevent some clients such as Postman from working properly.
This article explains how to use a public certificate from Let’s Encrypt with Red Hat Single Sign-On.</description></item></channel></rss>