Endless three loading dots of BBB for all users with OIDC's Azure credentials

[keithkhl]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. I use Social Login app's 'Custom OpenID Connect' for Microsoft account users to login to my self-hosted NextCloud.
2. I have Auth/Token URL, along with client Id/Secret, and Scope
3. My Scope is 'openid profile email offline_access User.Read' - which I use for Moodle
4. Users can login to the NextCloud website freely
5. But when users try to access BBB's open room, three dots are keep loading, and nothing else changes.

Expected behavior
User accounts that does not depend on OpenID have no issue to get connected to BBB's room. To make sure, both tries have been done with admin accounts.

Screenshots
If applicable, add screenshots to help explain your problem.

System (please complete the following information):

• Browser with version : Occurs to all browsers, Chrome, Edge, FireFoxk Opera (Desktop, Android, and iOS)
• App version : 2.7.2
• Nextcloud version : 30.0.1
• BigBlueButton version : 3.0.0-beta4 and 2.7.3 (Docker)
• Is your BigBlueButton instance working with Greenligh? Yes
• Did you enter your BBB API url and secret? Yes
• Are you using a load balancer, like Scalelite? For 3.0.0-beta4 no, but 2.7.3 Yes w/ proxy server's coturn

Nextcloud log:

REPLACE ME WITH YOUR NEXTCLOUD LOG

Javascript log:

REPLACE ME WITH YOUR JS LOG

Additional context
I have done a number of different set up cases, but all failed. Since it works with non-Azure accounts, I believe it is somehow related to necessary user information not delivered from Azure -> Nextcloud -> BBB, while I have no issue at all with Moodle w/ exactly the same set up.

For the record, I have checked with API permissions of all 5 components of 'Scope' that all of them are granted with admin consent. This actually was done for Moodle way before.

I also added all components (optional and groups, and ID/Access/SAML) in token configuration, which was not necessary for Moodle.

Could be due to Social Login app, but whichever the app it is the cause, I think it is due to some information not delivered to BBB server.

[keithkhl]

• Integration issue with BBB app zorn-v/nextcloud-social-login#484

Just in case, I also posted the same issue on Social Login app. Given that it is working fine with regular accounts on NextCloud and Azure accounts on Moodle, I do believe it is either Social Login or BBB app (or both) when it handles key user information. Most likely it is due to my mis-configuration, but cannot locate the missing piece.