<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OpenID Connect on Nicolas Massé</title><link>https://www.itix.fr/topics/openid-connect/</link><description>Recent content in OpenID Connect on Nicolas Massé</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 17 Apr 2020 00:00:00 +0200</lastBuildDate><atom:link href="https://www.itix.fr/topics/openid-connect/index.xml" rel="self" type="application/rss+xml"/><item><title>Secure your OpenShift 4 cluster with OpenID Connect authentication</title><link>https://www.itix.fr/blog/secure-openshift-4-openid-connect-authentication/</link><pubDate>Fri, 17 Apr 2020 00:00:00 +0200</pubDate><guid>https://www.itix.fr/blog/secure-openshift-4-openid-connect-authentication/</guid><description>&lt;p>OpenShift, starting with the version 4, is installed with a temporary administrator account, &lt;a href="https://docs.openshift.com/container-platform/4.3/authentication/remove-kubeadmin.html">kubeadmin&lt;/a>.
When searching for a definitive solution, it might be tempting to go for the very classical &amp;ldquo;login and password&amp;rdquo; prompt, backed by an &lt;a href="https://docs.openshift.com/container-platform/4.3/authentication/identity_providers/configuring-htpasswd-identity-provider.html">htpasswd file&lt;/a>.
But this is yet another password to remember!&lt;/p>
&lt;p>OpenShift can handle the &lt;a href="https://openid.net/connect/">OpenID Connect&lt;/a> protocol and thus offers Single Sign On to its users.
No additional password to remember: you can login to the OpenShift console with your &lt;a href="../use-google-account-openid-connect-provider/">Google Account&lt;/a> for instance.&lt;/p></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>Use your Google Account as an OpenID Connect provider</title><link>https://www.itix.fr/blog/use-google-account-openid-connect-provider/</link><pubDate>Fri, 27 Mar 2020 00:00:00 +0200</pubDate><guid>https://www.itix.fr/blog/use-google-account-openid-connect-provider/</guid><description>&lt;p>We have passwords everywhere: to unlock our computer, to reach our inbox, to login as root on our Raspberry PI, etc.
Unless you have a password vault to store your credentials securely, it is very difficult to keep all your credentials safe. With the OpenID Connect protocol, you can replace the individual passwords of every web application by a Google Login.&lt;/p>
&lt;p>This article goes through all the steps to use your Google Account as an &lt;a href="https://openid.net/connect/">OpenID Connect&lt;/a> provider and subsequent articles (check links at the bottom of this article) explain how to configure the different services and software to use your Google Account as an OpenID Connect provider.&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></channel></rss>