Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Multi-tenancy support #177

Open
ahmedhosameldein opened this issue Mar 6, 2022 · 5 comments
Open

Multi-tenancy support #177

ahmedhosameldein opened this issue Mar 6, 2022 · 5 comments
Labels
enhancement New feature or request help wanted Extra attention is needed In-Testing Feature in testing required feedback

Comments

@ahmedhosameldein
Copy link

Is your feature request related to a problem? Please describe.
We have a client that have users provisioned across 74 Azure AD tenants, and wants to utilize Microsoft Learn LTI

Describe the solution you'd like
We need to have a single deployment of Microsoft Learn LTI that can be used by all users in the 74 tenants (Support multi-tenancy)
As per the final comment in issue #134 "Note – These steps are not a workaround for proper Multi-Tenant behavior" , could you please document the steps for proper multi-tenant behavior

Describe alternatives you've considered
We tried the steps mentioned in issue # 134 , but still facing an issue (we are currently troubleshooting by adding extra logs):
#134

Additional context
Current issue we are facing:

  • We are using LTI 1.3
  • Initiate login succeed , and redirects to the LMS for login, and the LMS replies back with the token
  • The call for LTI advantage launch fails with null reference exception
@leestott
Copy link
Contributor

leestott commented Mar 8, 2022

@ahmedhosameldein at present he solution is not built to support multi tenant

If you have developer resources we would welcome contributions from the community

As per #134 this is enhancement to the current solution.

We would welcome community contributions on this feature

@leestott leestott added enhancement New feature or request help wanted Extra attention is needed labels Mar 8, 2022
@leestott
Copy link
Contributor

Request also #149

@warrenbuhler
Copy link
Contributor

Hi,

Would you be interested in testing out a change to the LTI that would support multi-tenant sign-on using Azure Business to Consumer?

I'm part of a UCL team that has been working with Lee at Microsoft to support multi-tenancy. We are finalizing a forked repo and expect to have it ready for testing within 1.5 - 2 weeks (targeting early August). We have done all our testing using Moodle which we have confirmed supports B2C authentication already.

You will need
• A B2C tenant -- you will need create one, but we have a script to help configure the remaining settings
• An LMS for testing (preferably Moodle)
• Two or more AD tenants to whitelist as part of testing

We are scripting as much of the setup and configuration as we can. So we expect the total work on your end to be about than 3 -7 hours, obviously changing based on how much testing you do.

If you are interested, I will reach back out on Github here when our changes are ready. We will have documentation ready and a form for you to fill out feedback on. We can also correspond on this issue thread if you have any issues, questions, or concerns.

Best,

Warren and the UCL Team

@leestott
Copy link
Contributor

leestott commented Aug 23, 2022

Update on the work by University College London - a team have been developing a solution for multiple Azure Active Directory and B2C connectivity see this fork for testing https://github.com/UCL-MSc-Learn-LTI/Learn-LTI/ the plans are for users to validate this fork and we will be working with the team to merge in features to the main branch.

@leestott leestott added the In-Testing Feature in testing required feedback label Aug 23, 2022
@leestott
Copy link
Contributor

leestott commented Aug 23, 2022

@ahmedhosameldein if you would like to test AAD B2C support please use this fork #149 https://github.com/UCL-MSc-Learn-LTI/Learn-LTI

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request help wanted Extra attention is needed In-Testing Feature in testing required feedback
Projects
None yet
Development

No branches or pull requests

3 participants