Securing the CLI with OAuth2 Machine Authorization

0
42
Securing the CLI with OAuth2 Machine Authorization


Most corporations have robust exterior safety, e.g. blocking all entry to manufacturing belongings utilizing a firewall, and requiring a VPN to get “inside” entry to manufacturing environments. Nevertheless, as soon as you’re related to the VPN, the inner techniques are often very poorly protected, and there may be little to no authentication and authorization for inside instruments and companies.

Two frequent threats to inside safety are compromised worker laptops and provide chain assaults. In these eventualities, the attacker operates behind the firewall, usually with unrestricted community entry.

Companies with an internet ui could be secured utilizing an software load balancer, e.g. an AWS ALB with OIDC, however how do you shield entry to command line interface (CLI) primarily based instruments? Requiring a username and password for each CLI invocation makes it painful to make use of and storing the credentials on the system leaves them broad open in case the pc they reside on is compromised.

The Command Line

Most inside instruments have a CLI to handle the companies which are used throughout the firm and lots of are poorly protected. What’s one of the simplest ways to authorize CLIs? And how will you tie authorization into the corporate’s SSO?

One choice is to deploy Hashicorp Vault, however that’s lots of setup and upkeep, so until you might have a crew to function it, Vault won’t be a very good match.

An alternative choice is the OAuth2 machine authorization grant (RFC8628), which is what this weblog publish will present you learn how to use.

The OAuth 2.0 machine authorization grant is designed for Web-connected units that both lack a browser to carry out a user-agent-based authorization or are enter constrained to the extent that requiring the person to enter textual content with a view to authenticate through the authorization circulate is impractical. It permits OAuth purchasers on such units (like good TVs, media consoles, digital image frames, and printers) to acquire person authorization to entry protected sources by utilizing a person agent on a separate machine.

In the event you ever used the AWS CLI with Single SignOn, that is what it does.

OAuth2 Machine Circulation

The Machine Authorization Circulation comprises two completely different paths; one happens on the machine requesting authorization (the CLI) and the opposite happens in a browser. The browser circulate path, whereby a tool code is certain to the session within the browser, happens as a parallel path half within the machine circulate path.


device-5

Implementing the OAuth Machine Circulation

Now we’ll have a look at what the above sequence diagram seems like when it’s carried out.

The inner CLI instrument at Rockset known as rsctl and is written in go. Step one is to provoke the machine circulate to get a JWT entry token.

$ rsctl login
Making an attempt to robotically open the SSO authorization web page in your default browser.
If the browser doesn't open otherwise you want to use a special machine to authorize this request, open the next URL:

https://rockset.auth0.com/activate?user_code=BBLF-JCWB

Then enter the code:
BBLF-JCWB

Efficiently logged in!

In case you are utilizing the CLI after logging in to a different laptop, e.g. ssh:ing to a Linux server, and you employ macOS, you possibly can configure iTerm to robotically open the hyperlink utilizing a “Run command” set off.

The web page that the hyperlink takes you to seems like this:


Device Confirmation


After you have confirmed that the “person code” is right (matches with what the CLI reveals), and also you click on “Verify”, it should take you thru the conventional OAuth2 login process (which in our case requires a username, password and {hardware} token).

As soon as the authentication is accomplished, you can be redirected and offered with a dialog just like the one under, and you’ll shut the browser window.


Device Confirmation


The CLI has now acquired a jwt entry token which is legitimate for quite a few hours and is used to authenticate by way of inside companies. The token could be cached on disk and reused between CLI invocations throughout its lifetime.

Once you concern a brand new rsctl command, it should learn the cached Entry Token from disk, and use it to authenticate with the inner APIs.

Beneath the Hood

We’ve got carried out and open sourced a go module to carry out the machine authorization circulate (github.com/rockset/device-authorization). It helps each Auth0 and Okta as OAuth suppliers.

Pattern Code

The next code is on the market within the instance listing within the git repository.

Embedded content material: https://gist.github.com/pmenglund/5ed2708cdb88b6a6982258aed59a0899

We now have a JWT token, which can be utilized to authenticate REST calls by setting the Authorization header to Bearer:

Embedded content material: https://gist.github.com/pmenglund/b2ac7bb15ce25755a69573f5a063cb14

It’s now as much as the receiving finish to validate the bearer token, which could be completed utilizing an AWS ALB with OIDC authentication or a supplier particular API from the API server.

Offline Validation

An alternative choice for entry token validation is “offline validation”. In offline validation, the API server will get the general public key used to signal the JWT token from the supplier (and caches the general public key) and performs the validation within the API server, as an alternative of constructing a validation request to the supplier.

Residual Danger

One factor this doesn’t shield towards is an attacker with a foothold on the pc that executes the CLI. They’ll simply wait till the person has accomplished the authentication, and they’ll then be capable to act because the person throughout the entry token.

To mitigate this threat, you possibly can require a one time password (OTP), e.g. a Yubikey, each time the person performs a privileged motion.

$ rsctl delete useful resource foobar
please enter yubikey OTP: ccccccvfbbcddjtuehgnfrbtublkuufbgeebklrubkhf
useful resource foobar deleted

Closing Ideas

On this weblog, we’ve got proven how we constructed and open-sourced a go module to safe the Command Line Interface (CLI) utilizing an OAuth2 machine authorization circulate that helps each Auth0 and Okta SSO suppliers. You possibly can add this go module to your inside instruments and scale back inside safety threats.



LEAVE A REPLY

Please enter your comment!
Please enter your name here