Chances are, the initial function was written when the underlying auth backend only supported a single account (structurally), and most clients were using that method.

Then later on, it was figured out that multiple accounts per credential set (?!?) needed to be supported, but the original clients still needed to be supported.

And either no one could afree on a sane convention if this happened (like returning the first from the list), or someone was told to ‘just do it’.

So they made the new call, migrated themselves, and put in a uncaught exception in the old place (can’t put any other type there without breaking the API) and blam - ticket closed.

Not that I’ve ever seen that happen before, of course.

Oh, and since the multi-account functionality is obviously new and probably quite rare at first, it could be years before anyone tracks down whoever is responsible, if ever.