Right, and the article makes it sound like a good thing that an SSO provider should be policing things

I've been very leery about the idea of letting companies own someone's credentials via SSO in general, so if it encourages at least diversification away from a few SSO providers, I'm kind of enthusiastic about SSO providers imposing restrictions on people using their services.

Yeah. You have to make a developer account to make an API token in order to setup any of those oauth options.

Granted, you could just put in random bullshit in the developer accounts, but generally I'd bet google would still know who the person involved is.

So I'm thinking back to the times I've used it. I want to say I assume they have a way to track where this is being used based on referrer, but I don't remember clearly enough. I don't think a given token has to be tied to any URL. You just get a token and validate it with a service.

But people who use it on a daily basis could probably answer more definitively. I've just used it a couple of times and didn't bother retaining it because it's easy to figure out when you need it.