<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cli on RedDec</title><link>https://blog.reddec.net/tags/cli/</link><description>Recent content in Cli on RedDec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 03 Apr 2024 09:37:07 +0800</lastBuildDate><atom:link href="https://blog.reddec.net/tags/cli/index.xml" rel="self" type="application/rss+xml"/><item><title>Oauth Token via CLI</title><link>https://blog.reddec.net/posts/oauth-token-via-cli/</link><pubDate>Wed, 03 Apr 2024 09:37:07 +0800</pubDate><guid>https://blog.reddec.net/posts/oauth-token-via-cli/</guid><description>&lt;p&gt;In today&amp;rsquo;s world of distributed systems and microservices, security has
become more critical than ever. One common approach to securing these
systems is through the use of OpenID Connect (OIDC), an identity layer
built on top of the OAuth 2.0 protocol. However, integrating OIDC into
command-line interface (CLI) applications can be challenging due to the complexity of OIDC flows.&lt;/p&gt;
&lt;p&gt;In this short article there is a use-case of using &lt;a href="https://github.com/cloudentity/oauth2c"&gt;oauth2c&lt;/a&gt; to obtain token via CLI.
Keycloak is used as primary refernce of IDP, but any other OIDC complient solutions should work in the same way.&lt;/p&gt;</description></item></channel></rss>