Colin, being the hero that he is, made it so that build.snapcraft.io didn't need to bounce you through SSO *and* the developer portal as part of on-boarding. We should do the same for the snapcraft command line, such that you can create an account and get started just by being redirected through SSO. Context follows: [11:30am] ev: cjwatson: I mean in creating a developer account to upload snaps with [11:31am] ev: basically, can someone get started from snapcraft by only hitting a single site, SSO [11:32am] cjwatson: ev: Oh, right. Sure, if snapcraft requests the edit_account permission in its ACL request to SCA, then it can POST to /dev/api/agreement/ to accept the terms of service. [11:33am] ev: NICE [11:33am] ev: thank you [11:33am] cjwatson: ev: Or actually, it doesn't even need edit_account for that; the macaroon it already acquires will do. [11:34am] cjwatson: ev: That was all already in place before I touched anything. What I did was to make it possible to set the short developer namespace over the API, and *that's* what requires the edit_account permission. [11:34am] ev: ah [11:35am] cjwatson: (That's PATCH /dev/api/account with { "short_namespace": "whatever" } as the body.) [11:35am] cjwatson: Anyway, both are indeed possible in snapcraft too.