Folks did a great job at build distinguishing "supported" SSO flows, for apps, server-side apps, server-side apps that have UIs, etc etc. In particular "openid connect" was distinguished from "oauth2", the former pertaining only to browsers talking to webapps, that want to consume APIs offered by component services. Rubbish terminology from oauth2 standards and lots of legacy is nicely avoided, having made "clean start".
SO, I went to the WAB sample code and fiddled around with it so AAD is added to the accounts manager, of a store app. Since this is (in old terminology) the userlogin process for an app, we want the users name to be presented. Nicely, AAD presented me, via WAB and a clientID attached to a "native app" registration, with access token and IDtoken. The latter had some user names within, used in login/account flyouts etc.
Now, is this an openid connect flow? (where WAB plays the role of the browser, in the definition)?
Or is an oauth2 flow that just happens to have an idtoken thrown in, too?