Getting in touch

Email: sag@resoauth.email.

Phone: +44 1202 158814 (leave a voicemail).

Post: RESOAuth Ltd, Lytchett House, 13 Freeland Park, Wareham Road, Poole, Dorset, BH16 6FA, United Kingdom.

RESOAuth Ltd is registered in England and Wales, company number 15175188.

For bugs and technical questions, the issue tracker is usually faster than any of the above.

Reporting a bug, asking for a change, contributing

SAG is open source, and everything below happens in public on the code repository rather than here:

• A bug, including one in these pages: open an issue. Say what you did, what happened, and what you expected. Existing issues are searchable, so a look first sometimes answers it faster.
• A change or a new feature: an issue again, describing the problem rather than the patch. Larger ideas are written up as RFCs, and reading the open ones shows what is already being considered.
• Code or documentation: CONTRIBUTING.md explains the process, what a change needs before it is reviewed, and the standard tests are held to. This site has its own repository, sag-user-docs, and every page has an "edit this page" link at the bottom.

Reporting a security vulnerability

Not in a public issue. Use the private route in SECURITY.md, which is GitHub's private vulnerability reporting on the code repository. That page says which versions are supported, what to put in a report, and how long an acknowledgement should take.

Want a dedicated instance on your own domain, or help configuring your own deployment? See custom instances and professional services.