Moodle Tab in Teams Requires Sign In

%3CLINGO-SUB%20id%3D%22lingo-sub-1502176%22%20slang%3D%22en-US%22%3EMoodle%20Tab%20in%20Teams%20Requires%20Sign%20In%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1502176%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20pretty%20much%20successfully%20integrated%20Moodle%20with%20Teams%20(Team%20creation%20upon%20Moodle%20course%20creation%2C%20user%20enrollment%20sync%2C%20etc...)%20with%20the%20exception%20of%20one%20piece.%26nbsp%3B%20The%20Moodle%20Tab%2C%20created%20in%20each%20Team%2C%20requires%20the%20user%20sign%20in%20again%20to%20O365.%26nbsp%3B%20It%20was%20my%20understanding%20that%20the%20integration%20would%20handle%20the%20authentication%20via%20OpenID%20Connect%20and%20the%20%22enable%20authenticated%20users%20to%20create%20web%20tokens%22%20setting.%26nbsp%3B%20I%20realize%20the%20Moodle%20tab%20is%20just%20an%20iFrame%20essentially%2C%20but%20am%20I%20mistaken%20that%20this%20is%20not%20how%20the%20integration%20works%3F%26nbsp%3B%20Will%20our%20users%20just%20have%20to%20sign%20in%20again%20to%20access%20Moodle%20content%20in%20that%20tab%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1502176%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

We've pretty much successfully integrated Moodle with Teams (Team creation upon Moodle course creation, user enrollment sync, etc...) with the exception of one piece.  The Moodle Tab, created in each Team, requires the user sign in again to O365.  It was my understanding that the integration would handle the authentication via OpenID Connect and the "enable authenticated users to create web tokens" setting.  I realize the Moodle tab is just an iFrame essentially, but am I mistaken that this is not how the integration works?  Will our users just have to sign in again to access Moodle content in that tab?

5 Replies

Hi @KyleGrizzell ,

 

Just double checking, was it this setup that you followed?

 

https://docs.microsoft.com/en-us/microsoftteams/platform/moodleinstructions

 

Thanks

 

Henry

Yup, that’s the one.

@KyleGrizzell 

 

We have been setting this up recently and I have been through the documentation many times and have the same thing.

Moodle is able to create the Teams from the chosen course and add the Moodle tab but then we are presented with the following:

SBirkett_0-1593698558547.png

We have to login to Office 365 and then it'll ask us to login to our Moodle before it presents the course content correctly.  Once we have logged in we can go to other Teams which have the Moodle tab during the same Teams session and not have to log in again but the next time we use Teams we will to go through the same login process.  This happens for Teams Web app or Teams Desktop.

I'd really appreciate any suggests to sort this out as we want to go live with this asap.




@SBirkett 

 

Check this thread out over at GitHub. 

 

https://github.com/microsoft/o365-moodle/issues/1319

 

Looks like that's just how it works and there's no workaround.  I've noticed the integration works best via web browser versus the standalone desktop app though.  Chrome or Edge would be the best option, since it has the most functionality with regard to video chat (if that's needed).

I also got this error. I tried   new install moodle and  setting up integration countless time but no luck. 

 

In Teams Desktop app , tab is just empty. 

In Web App it fetches course list for 1 or 2 seconds but then redirects to dialog manual login  or Login to office365. Logging in again doesnt work.

 

During  teams web tab add phase, i run developor tools and generated following   errors : 

 

2021-01-22T12:19:16.476Z AUTHMSAL: Event: adal:tokenRenewFailure, code: invalid_resource|AADSTS500011: The resource principal named api://xxxxx.westeurope.cloudapp.azure.com/xxxxxxx-xxxx-xxxxx-xxxx-8b6997159a90 was not found in the tenant named xxxxxxxxx-xxxxxx-xxxxx-xxxx-xxxxxxxxxxx. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant.
Trace ID: 2e944688-a460-40bf-b95a-d62d8bda1400
Correlation ID: 98c4e1b6-b248-4101-afa0-3cefc70e009c
Timestamp: 2021-01-22 12:19:15Z, resource: api://xxxxxxxxxx.westeurope.cloudapp.azure.com/xxxxxxx-xxxx-xxxxx-xxxx-8b6997159a90, action: resourceDisabled

 

any suggestions ?