OmniAuth strategy for Bolt

OmniAuth strategy for Citadele Banklink

Simple gem to enable rack powered Ruby apps to authenticate via REST with an enterprise CAS authentication server via X509 client certificates.

OmniAuth strategy for Luminor (DNB) Link

OmniAuth strategy for GlobaliD

OmniAuth strategy for Lightning Network

Custom OmniAuth strategy for OpenID Federation providers using openid_connect gem, supporting signed request objects (RFC 9101), ID token encryption/decryption, client assertion (private_key_jwt), and OpenID Federation entity statements. Framework-agnostic and works with Rails, Sinatra, Rack, and other Rack-compatible frameworks.

Protects your Rails app from Omniauth request phase CSRF vulnerability.

OmniAuth strategy for Swedbank Banklink

A generalized Rack middleware for importing group contacts from gmail.

A generalized framework for multiple-provider webhooks subscriptions.

Payment gateway abstraction for rack applications. Think omniauth for off-site payment.

Another LaMe Web Frame-work

A Rack middleware to make URLs in one-page webapps easier. In a couple of recent projects, I've needed to avoid full page refreshes as much as possible. In the first, I wanted to keep an embedded music player active while the user was browsing. In the second, I just wanted fancier transitions between pages. It's possible to do this in an ad-hoc way, but I very quickly got tired of hacking things together. Enter Onesie. Onesie congealed from these requirements: * I want a one-page web app, * But I want the back button to work, * And I want search engines to still index some stuff, * And I (mostly) don't want to change the way I write a Rails/Sinatra app. If someone visits <tt>http://example.org/meta/contact</tt>, I want them to be redirected to <tt>http://example.org/blah/#/meta/contact</tt>, but after the redirection I still want the original route to be rendered for search engine indexing, etc. When Onesie gets a request, it looks to see if under your preferred one-page app path ("blah" in the example above). If it's not, Onesie sets the current request's path in the session and redirects to your app path. If a request is under the one-page app path, the "real" request's path is retrieved from the session and used for subsequent routing and rendering. This means that, as above, a request for http://example.org/meta/contact Will be redirected to http://example.org/blah/#/meta/contact But still render the correct action in the wrapped app, even though URL fragments aren't passed to the server. This is a terrible explanation. I'll write a sample app or something soon.

Ruby wrapper around the ONS OpenAPI making easy to quickly retrieve data. It may not expose the full functionality of the ONS OpenAPI.

Simple configurable application healthcheck rack middleware.

Captures unhandled exceptions from web requests and background jobs, enriches them with request/user/server context, and delivers structured JSON payloads to configurable webhook endpoints. Works with any Rack-based framework; optional Rails integration included.

High performance Rack server for Opal and Ruby

A Ruby gem that generates OpenAPI 3.0 documentation from Minitest integration tests in Rails applications. Uses serializers as the single source of truth for response schemas.

A unified OpenAPI toolkit for Rails that combines test-driven spec generation, reusable schema components as Ruby classes, and runtime request/response validation middleware. Supports OpenAPI 3.0 and 3.1. Works with both RSpec and Minitest.