RubyGems + KeySigner

Use KeySigner to generate one-time codes for a RubyGems.org account.

What to check first

Choose a test account that owns no gems. Keep the browser session open and have somewhere secure to save the recovery codes RubyGems.org shows after enrollment.

KeySigner setups

KeySigner setup requirements →

What it covers

This test covers browser sign-in. Release commands and trusted publishing have their own authentication requirements.

Make an offline recovery plan →

Troubleshooting

Does the test account reject your enrollment code?

Confirm the KeySigner entry belongs to that account and try a new code before it expires. If RubyGems.org expired the enrollment QR code, start registration again with the new QR code.

Two-factor codes for PyPI, RubyGems and Docker Hub →

Check RubyGems status for reports on the RubyGems.org package registry.

Find documentation and support →

Documentation and support

RubyGems documentation

Register an authenticator on RubyGems.org
Use a recovery code
Set up trusted publishing for a gem

KeySigner setup help

Ask about this setup →