Problem/Motivation
Now it is not possible to use multiple connectors for Office 365, it is will be helpful for users from different organisations.
Proposed resolution
1. Create config entity type to make possible create multiple connectors.
2. Existing configurations set as "default" entity.
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #17 | use-multiple-o365-connectors-3240633-17.patch | 42.53 KB | fabianderijk |
| #16 | use-multiple-o365-connectors-3240633-16.patch | 44.36 KB | fabianderijk |
| #15 | interdiff_11-15.txt | 1.25 KB | ronaldtebrake |
| #15 | use-multiple-o365-connectors-3240633-15.patch | 38.28 KB | ronaldtebrake |
| #11 | use-multiple-o365-connectors-3240633-11.patch | 36.8 KB | robertragas |
Issue fork o365-3240633
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
tbkot commentedComment #4
tbkot commentedComment #5
fabianderijkThis looks promising. I'll take a look at the merge request and let you know.
Currently we are working on a better 3.x branch so, if this patch works, i'll add it to the new branch as well.
Comment #6
fabianderijkComment #7
rolki commentedIt would be grate to have this change in 3.x. The only thing that we probably should do is deprecate current configuration settings since we already will have configuration entities instead.
Comment #8
rolki commentedI reviewed changes, fixes some things (CS and use capabilities of PHP 7.1). See https://git.drupalcode.org/project/o365/-/merge_requests/8/diffs?commit_...
Changes look good to me, but anyway we should retest it I guess.
Comment #9
tbkot commentedComment #10
rolki commentedHi, are there any update here? Have you been able to view the changes?
Comment #11
robertragas commentedAttached a patch for the dev 3.x branch.
Comment #13
fabianderijkI've just pushed the 2.0.x branch, and currently are looking at the patch for the 3.0.x branch.
Comment #14
fabianderijkI've created a new MR for the 3.0.x branch. Currently the login is not working correctly with the patch. This still needs some work.
https://git.drupalcode.org/project/o365/-/merge_requests/11
Comment #15
ronaldtebrake commentedI've added remarks on the MR, just noticed at least one fix from the MR that broke the login in the patch.
So for reference sake here is an interdiff and patch update from 11, with that feedback in mind.
Comment #16
fabianderijkI've worked on this issue in the merge request. For me, the code there works. Here's the patch so you test this as well.
Let me explain some things as well:
* The client ID, secret, etc are removed from the entity. They are saved and loaded from the settings.php. This is done because of safety reasons.
* The scope is automatically generated from the implemented hook_o365_auth_scopes() hooks.
Comment #17
fabianderijkHere's an updated patch based on the work in 3.0.x we have done the last days.
Comment #18
codebymikey commentedOne thing of note is that although this was released as part of a patch release from 2.0.4 -> 2.0.5, it actually breaks existing installations since they'll need update their Active Directory Redirect URIs to point to /o365/callback/default rather than /o365/callback going forward.
So it'd be helpful if the release note could mention this. One way to avoid the breaking change might be to provide a default route for /o365/callback which redirects to the first connector it can find or "default" if it's available.
Comment #19
bramdriesenFix typos
Comment #20
rolki commentedComment #21
rolki commentedComment #22
rolki commentedAll next work with adding this functionality will be done within https://www.drupal.org/project/o365/issues/3240633, I would propose to close this ticket and continue communication in new one.
Comment #23
rolki commentedComment #24
bramdriesenYou linked to this issue? And it has a merged commit, so I would not close this one as a duplicate actually.
Comment #25
fabianderijkI'm closing this as an duplicate. The linked issue has been fixed . The 2.x branch isn't supported anymore.