File: README — Documentation by YARD 0.9.45

# 🖥️ OAuth::TTY

`if ci_badges.map(&:color).detect { it != "green"}` ☝️ let me know, as I may have missed the discord notification.

`if ci_badges.map(&:color).all? { it == "green"}` 👇️ send money so I can do more of this. FLOSS maintenance is now my full-time job.

👣 How will this project approach the September 2025 hostile takeover of RubyGems? 🚑️

I’ve summarized my thoughts in this blog post.

## 🌻 Synopsis

OAuth 1.0a is an industry-standard protocol for authorization.
It is an update to the original OAuth 1.0 protocol, and is used by many popular services.

This RubyGem provides a CLI for OAuth 1.0 or 1.0a clients and servers in Ruby applications.

All dependencies of this gem are signed, so it can be installed with a `HighSecurity` profile.

- OAuth 1.0 Spec
- oauth sibling gem for OAuth 1.0 / 1.0a client and server implementations in Ruby.
- oauth2 sibling gem for OAuth 2.0 / 2.1, & OIDC client implementations in Ruby.

## 💡 Info you can shake a stick at

Tokens to Remember |
--- | ---
Works with JRuby |
Works with Truffle Ruby |
Works with MRI Ruby 4 |
Works with MRI Ruby 3 |
Works with MRI Ruby 2 |
Support & Community |
Source |
Documentation |
Compliance |
Style |
Maintainer 🎖️ |
`...` 💖 | 🧊 🐙 🛖 🧪

### Compatibility

Compatible with MRI Ruby 2.3.0+, and concordant releases of JRuby, and TruffleRuby.
CI workflows and Appraisals are generated for MRI Ruby 2.4+.
This test floor is configured by `ruby.test_minimum` in `.kettle-jem.yml` and
may be higher than the gem’s runtime compatibility floor when legacy Rubies are
not practical for the current toolchain.

The amazing test matrix is powered by the kettle-dev stack.

How kettle-dev manages complexity in tests

Gem | Source | Role | Daily download rank
--- | --- | --- | ---
appraisal2 | GitHub | multi-dependency Appraisal matrix generation |
appraisal2-rubocop | GitHub | RuboCop Appraisal generator integration |
kettle-dev | GitHub | development, release, and CI workflow tooling |
kettle-jem | GitHub | Appraisals & CI workflow templates |
kettle-soup-cover | GitHub | SimpleCov coverage policy and reporting |
kettle-test | GitHub | standard test runner and coverage harness |
rubocop-lts | GitHub | Ruby-version-aware linting |
turbo_tests2 | GitHub | parallel test execution |

### Federated DVCS

Find this repo on federated forges (Coming soon!)

Federated DVCS Repository | Status | Issues | PRs | Wiki | CI | Discussions
--- | --- | --- | --- | --- | --- | ---
🧪 ruby-oauth/oauth-tty on GitLab | The Truth | 💚 | 💚 | 💚 | 🐭 Tiny Matrix | ➖
🧊 ruby-oauth/oauth-tty on CodeBerg | An Ethical Mirror (Donate) | 💚 | 💚 | ➖ | ⭕️ No Matrix | ➖
🐙 ruby-oauth/oauth-tty on GitHub | Another Mirror | 💚 | 💚 | 💚 | 💯 Full Matrix | 💚
🎮️ Discord Server |  | Let’s | talk | about | this | library!

### Enterprise Support

Available as part of the Tidelift Subscription.

Need enterprise-level guarantees?

The maintainers of this and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source packages you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact packages you use.

- 💡Subscribe for support guarantees covering all your FLOSS dependencies
- 💡Tidelift is part of Sonar
- 💡Tidelift pays maintainers to maintain the software you depend on!
  📊`@`Pointy Haired Boss: An enterprise support subscription is “never gonna let you down”, and supports open source maintainers

Alternatively:

## ✨ Installation

Install the gem and add to the application’s Gemfile by executing:

    bundle add oauth-tty

If bundler is not being used to manage dependencies, install the gem by executing:

    gem install oauth-tty

## ⚙️ Configuration

The oauth-tty gem is a thin CLI over the oauth gem. You supply your consumer credentials, token credentials (when applicable), a target URI, and optional parameters, and the tool signs requests or helps you complete an OAuth 1.0/1.0a 3-legged flow.

What you can configure

- Locations for OAuth parameters:
  - –header (default): send OAuth params in Authorization header
  - –body: send OAuth params in the request body
  - –query-string: send OAuth params on the query string

- HTTP method: –method GET | POST | PUT | DELETE | … (default: POST)

- Signature method: –signature-method HMAC-SHA1 | RSA-SHA1 | PLAINTEXT (default: HMAC-SHA1)

- OAuth version: –version 1.0 (default: 1.0) or –no-version to omit
- Nonce/timestamp: auto-generated by default; can be overridden via –nonce and –timestamp
- Verbose output: –verbose prints the full signing breakdown, headers, and signature base string
- XMPP mode: –xmpp emits OAuth as an XMPP stanza instead of HTTP artifacts

Required inputs (by command)

- sign, query: –consumer-key, –consumer-secret, –token, –secret, and –uri
- authorize: –consumer-key, –consumer-secret, the OAuth endpoints below, and –uri (service resource you’re authorizing for)

Authorization endpoints (for oauth authorize)

- –request-token-url URL
- –authorize-url URL
- –access-token-url URL
- Optional: –callback-url URL (for 1.0a), –scope SCOPE (provider-specific)

Providing options

- CLI flags (preferred for quick usage)
- Options file: use -O or –options to read additional arguments from a file. The file is tokenized by whitespace; put the same flags you’d pass on the command line, spread across lines as needed.

Example options file (oauth.opts)

    --consumer-key ck_123
    --consumer-secret cs_456
    --token at_789
    --secret ats_abc
    --method GET
    --uri https://api.example.com/v1/profile
    --parameters foo:bar
    --parameters "status=active"
    --header

Run with: oauth sign -O oauth.opts

Defaults at a glance

- scheme: header
- method: POST
- signature method: HMAC-SHA1
- oauth_version: 1.0 (omit with –no-version)
- nonce, timestamp: auto-generated each run

Tips

- For parameters you can use either key:value or already-escaped pairs like key=value. Repeat –parameters to add multiple pairs.
- When using –body, only methods that support bodies should be used (e.g., POST/PUT/PATCH).
- Some providers require exact parameter ordering and inclusion; use –verbose to see normalized parameters and the signature base string.

## 🔧 Basic Usage

In a shell run `oauth` to start the console.

Quick help and version

    oauth --help
    oauth --version  # or oauth -v

Sign a request (minimal)
Print just the OAuth signature value for a GET request:

    oauth sign \
      --consumer-key ck \
      --consumer-secret cs \
      --token at \
      --secret ats \
      --method GET \
      --uri "https://api.example.com/v1/resource?limit=10"

Sign a request (verbose, header output)

    oauth sign \
      --consumer-key ck \
      --consumer-secret cs \
      --token at \
      --secret ats \
      --method POST \
      --uri https://api.example.com/v1/resource \
      --parameters "status=active" \
      --header \
      --verbose

This prints OAuth parameters, normalized parameters, signature base string, Authorization header, and both raw and escaped signatures.

Query a protected resource
Performs the signed HTTP request and prints the HTTP status and body.

    oauth query \
      --consumer-key ck \
      --consumer-secret cs \
      --token at \
      --secret ats \
      --method GET \
      --uri https://api.example.com/v1/profile \
      --parameters "fields=id,name"

Notes:

- The CLI will append any –parameters to the request URI’s query string and sign the request.
- Use –body or –header/–query-string to influence where OAuth params go; query also constructs OAuth via the consumer internally.

Start an OAuth 1.0a authorization flow
Guides you to obtain an access token and token secret from a provider.

    oauth authorize \
      --consumer-key ck \
      --consumer-secret cs \
      --request-token-url https://provider.example.com/oauth/request_token \
      --authorize-url https://provider.example.com/oauth/authorize \
      --access-token-url https://provider.example.com/oauth/access_token \
      --callback-url https://yourapp.example.com/oauth/callback

What happens:

- You’ll be shown an authorization URL to open in a browser.
- After approving, the provider shows a verifier (PIN). Paste it back into the prompt.
- The tool prints the access token and secret under “Response:”. Save those and use them with sign/query.

Using an options file

    oauth sign -O oauth.opts

You can still add/override flags after -O; later flags win.

For more examples

- Run any command without args to see its specific help.
- Browse the specs under spec/oauth/tty for additional scenarios and edge cases.

In a shell run `oauth` to start the console.

For now, please see the tests for other usage.

## 🦷 FLOSS Funding

While ruby-oauth tools are free software and will always be, the project would benefit immensely from some funding.
Raising a monthly budget of… “dollars” would make the project more sustainable.

We welcome both individual and corporate sponsors! We also offer a
wide array of funding channels to account for your preferences.
Currently, Open Collective is our preferred funding platform.

If you’re working in a company that’s making significant use of ruby-oauth tools we’d
appreciate it if you suggest to your company to become a ruby-oauth sponsor.

You can support the development of ruby-oauth tools via
GitHub Sponsors,
Liberapay,
PayPal,
Open Collective
and Tidelift.

📍 NOTE
If doing a sponsorship in the form of donation is problematic for your company from an accounting standpoint, we’d recommend the use of Tidelift, where you can get a support-like subscription instead.

### Open Collective for Individuals

Support us with a monthly donation and help us continue our activities. [Become a backer]

NOTE: kettle-readme-backers updates this list every day, automatically.

No backers yet. Be the first!

### Open Collective for Organizations

Become a sponsor and get your logo on our README on GitHub with a link to your site. [Become a sponsor]

NOTE: kettle-readme-backers updates this list every day, automatically.

No sponsors yet. Be the first!

### Another way to support open-source

I’m driven by a passion to foster a thriving open-source community – a space where people can tackle complex problems, no matter how small. Revitalizing libraries that have fallen into disrepair, and building new libraries focused on solving real-world challenges, are my passions. I was recently affected by layoffs, and the tech jobs market is unwelcoming. I’m reaching out here because your support would significantly aid my efforts to provide for my family, and my farm (11 🐔 chickens, 2 🐶 dogs, 3 🐰 rabbits, 8 🐈‍ cats).

If you work at a company that uses my work, please encourage them to support me as a corporate sponsor. My work on gems you use might show up in `bundle fund`.

I’m developing a new library, floss_funding, designed to empower open-source developers like myself to get paid for the work we do, in a sustainable way. Please give it a look.

Floss-Funding.dev: 👉️ No network calls. 👉️ No tracking. 👉️ No oversight. 👉️ Minimal crypto hashing. 💡 Easily disabled nags

## 🔐 Security

See SECURITY.md.

## 🤝 Contributing

If you need some ideas of where to help, you could work on adding more code coverage,
or if it is already 💯 (see below) check issues or PRs,
or use the gem and think about how it could be better.

We so if you make changes, remember to update it.

See CONTRIBUTING.md for more detailed instructions.

### 🚀 Release Instructions

See CONTRIBUTING.md.

### Code Coverage

Coverage service badges

### 🪇 Code of Conduct

Everyone interacting with this project’s codebases, issue trackers,
chat rooms and mailing lists agrees to follow the .

## 🌈 Contributors

Made with contributors-img.

Also see GitLab Contributors: https://gitlab.com/ruby-oauth/oauth-tty/-/graphs/main

⭐️ Star History

</a>

## 📌 Versioning

This library follows for its public API where practical.
For most applications, prefer the Pessimistic Version Constraint with two digits of precision.

For example:

    spec.add_dependency("oauth-tty", "~> 1.0")

📌 Is "Platform Support" part of the public API? More details inside.

Dropping support for a platform can be a breaking change for affected users. If a release changes supported platforms, it should be called out clearly in the changelog and versioned with that impact in mind.

To get a better understanding of how SemVer is intended to work over a project’s lifetime, read this article from the creator of SemVer:

- “Major Version Numbers are Not Sacred”

See CHANGELOG.md for a list of releases.

## 📄 License

The gem is available as open source under the terms of
the MIT .

### © Copyright

See LICENSE.md for the official copyright notice.

Copyright holders

- Copyright (c) 2022, 2025-2026 Peter H. Boling
- Copyright (c) 2025 Aboling0
- Copyright (c) 2025 Annibelle Boling

## 🤑 A request for help

Maintainers have teeth and need to pay their dentists.
After getting laid off in an RIF in March, and encountering difficulty finding a new one,
I began spending most of my time building open source tools.
I’m hoping to be able to pay for my kids’ health insurance this month,
so if you value the work I am doing, I need your support.
Please consider sponsoring me or the project.

To join the community or get help 👇️ Join the Discord.

To say “thanks!” ☝️ Join the Discord or 👇️ send money.

💌 💌 💌

### Please give the project a star ⭐ ♥.

Many parts of this project are actively managed by a kettle-jem smart template utilizing StructuredMerge.org merge contracts.

Thanks for RTFM. ☺️

| Field | Value |
|—|—|
| Package | oauth-tty |
| Description | 🖥️ OAuth 1.0 / 1.0a TTY Command Line Interface |
| Homepage | https://github.com/ruby-oauth/oauth-tty |
| Source | https://github.com/ruby-oauth/oauth-tty |
| License | `MIT` |
| Funding | https://github.com/sponsors/pboling, https://ko-fi.com/pboling, https://liberapay.com/pboling/donate, https://opencollective.com/ruby-oauth, https://thanks.dev/u/gh/pboling, https://tidelift.com/funding/github/rubygems/oauth-tty, https://www.buymeacoffee.com/pboling |