Determine Social Provider Login Support (Facebook, Google) with StaticWebApps & App Service

[seantleonard]

Evaluate whether social providers include roles in their access tokens, i.e. via a role claim.

• If role claim(s) are included:
  • Can an end user can arbitrarily add themselves to roles or is that capability limited to FB app/enterprise admins?
    • If users can arbitrarily add themselves to roles, ensure we do NOT honor those roles to determine access in DAB engine and see whether SWA/AppService passes those roles through in the EasyAuth payload.
    • If just enterprise admins can manage roles/role assignments, no issues.
      • Check whether SWA/AppService passes those roles through in the EasyAuth payload. If not, developers must manage roles through SWA Azure Function Integration.
• No Role claims included:
  • Developers must manage roles through SWA Azure Functions (preview) Integration.

[StephanEggermont]

Default branch for gitlab is main too according to the documentation

[onierstrasz]

🤷‍♂️When I created a blank project and loaded it into GT I got a master branch.

[hellerve]

Is this gitlab.com or a self-hosted GitLab instance? If it’s self-hosted, which version is it? On gitlab.com, the default branch is indeed main; I just created one myself.

[onierstrasz]

Good question. I thought it was gitlab.com, but maybe it is a unibe hosted instance. I'll have to check!

[hellerve]

Thank you! In the meantime, I’ve fixed the other issue. The parser should now also handle gitlab.com (but not self-hosted instances!). It will also throw a hopefully more instructive error when trying to add the Baseline information to the README otherwise.

[onierstrasz]

Nice! Though there seems to be an unnecessary st now in the installation script. Can you please check, @hellerve ?

[hellerve]

I didn’t change it, but that is a Smalltalk syntax cue (https://www.markdownguide.org/extended-syntax/#syntax-highlighting). It should be supported by GitHub, GitLab, and GT.

[onierstrasz]

That's odd. Until I deleted it, it messed up the display of the README on my test repo on GitLab. Can't we get rid of it?

[onierstrasz]

Well, now I can't reproduce the problem. I will have to create a new repo and see if I can recreate the issue ...

[onierstrasz]

OK, I verified that it does not work in GitLab. Is it possible to remove the st syntax cue for GitLab?

[girba]

Can you try adding an empty line after Installation?

Also, if that does not help, what happens if you use smalltalk instead of st?

[onierstrasz]

Oh, with Andreas we discovered that the problem is that the newlines are wrong, not the st! Just editing the README on the GitLab web page and saving it fixes the issues.

[hellerve]

Hm, it looks like GitLab expects specific newlines where GitHub is happy with any. We are not doing anything specific to the newlines in the file, so this is the default behaviour with regards to newlines.

I’ll leave the st as is for now, then.