harness-multitool

0019 — A subscription sign-in ships where the vendor documents it for other apps

Decision

ADR 0003 kept every consumer subscription out of what the project ships, because vendors may restrict their use outside their own clients. That reason does not hold where the vendor itself publishes a sign-in for apps like this one. So the project ships a subscription sign-in only on that ground:

The rest of ADR 0003 stands: the Auth interface is public, and what a user builds for their own local build is that user's responsibility.

Why not take a vendor's own client id

Reusing another client's id would present this harness as that client. The documented flow needs no such thing.

Note

A vendor's terms can change. If one withdraws its flow, the adapter goes; this is not legal advice.

This page's source