HI,
I replicated the problem with PostgreSQL:
Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[42P10]: Invalid column reference: 7 ERROR: for SELECT DISTINCT, ORDER BY expressions must appear in select list LINE 5: ORDER by b.weight ^: SELECT DISTINCT * FROM "book" as b inner join "node" as n ON n.nid = b.nid WHERE b.pid = :pid ORDER by b.weight; Array ( [:pid] => 1 ) in Drupal\booktree\Controller\BooktreeController->booktree_mostra_figli() (line 69 of /var/www/html/booktree-pgsql/web/modules/contrib/booktree/src/Controller/BooktreeController.php).
the patch fixes it.
Thank you
I apply the fix to both branches 8.x-1.x and 3.x
HI,
Thanks for the report.
I quickly tried the module with 10.2.5 and SQlite but I don't encounter any problems.
What problems do you have with postgres?
The query is objectively not beautiful but it should still work...
Merged!
I can confirm that version 2.x-dev works correctly with drupal 10
Drupal 10.1.5: Patch #8 solved it.
@jsacksick we understood that the module uses "content entity" and not "config entity" however all the rest of commerce exports and imports its configurations and makes it possible to version the ecommerce.
Would it be possible to think about converting the approach and having config entities?
I'm closing the request because it's very old
I'm closing the request because I don't believe Drupal 5 exists anymore
I'm closing the request because I don't believe Drupal 5 exists anymore
After 11 years of waiting for feedback I think I can close it!
the example did not intercept exceptions, I made the example usable by users without having to correct the example.
I have been successfully using the above-mentioned versions and the relevant patch of comment 47 for a few months now.
@frank8199 are you sure you have configured azure correctly?
Are you using V2 of the microsoft integration?
I had the same problem when I didn't put the "openid" privilege.
Using the module I felt like having a full logout also on Azure and not only on Drupal but it didn't work...
In my version of azure( B2C + v2) the logout path is very different from "https://login.microsoftonline.com/common/oauth2/v2.0/logout?post_logout_..." and it didn't go.
I enclose a patch for version 8.x-1.4 which allows you to specify a custom logout path.
The patch is based on patch 33 โ
Thank you
@webflo
I confirm that patch 45 solves all the problems of beta4 for Azure B2C users.
In summary, those who need to use Azure AD B2C authentication can choose:
Branch 1.x (current stable)
- - openid_connect:8.x-1.2
- - openid_connect_windows_aad:8.x-1.4 + patch-33 โ
Branch 2.x (beta)
- - openid_connect:2.0.0-beta3
- - openid_connect:beta-2.0.0-beta4 + patch-45 โ
IMHO the beta branch could include the 45 ... but I leave the hard decision to the maintainers.
I remain available to test patches (@webflo contact me in PVT when you want)
@webflo
how I would love it if the problem was just configuration :(
To prevent any "migration" I uninstalled the modules cleaned the caches and after via composer installed everything including patching.
@webflo
I installed the beta4 with composer:
After login drupal goes to WSOD.
the crash log is:
TypeError: Drupal\openid_connect_windows_aad\Plugin\OpenIDConnectClient\WindowsAad::retrieveUserInfo(): Argument #1 ($access_token) must be of type string, null given, called in /var/www/html/tp.eutelsat.com/web/modules/contrib/openid_connect/src/OpenIDConnect.php on line 235 in Drupal\openid_connect_windows_aad\Plugin\OpenIDConnectClient\WindowsAad->retrieveUserInfo() (line 348 of /var/www/html/uccio3021812/web/modules/contrib/openid_connect_windows_aad/src/Plugin/OpenIDConnectClient/WindowsAad.php)
the problem is due to the missing access_token.
In the Microsoft response it does not include it if there is openid in the scope.
I think the change of fix_33 โ should be ported to the 2.x branch
Thanks for the suport
@webflow
For version openid_connect:8.x-1.2 + patch ( patch โ )
I use this configuration:
I gladly try version 2.x
I use these versions: openid_connect:2.0.0-beta3 + openid_connect:beta-2.0.0-beta4 + (patchv2) โ
Or should I start from the 2.x development branch and apply the patch?
Let me know which of the two ways you prefer.
I thank everyone for the work done.
I have installed many variants and tried several patches to get a working authentication with Azure AD B2C
At the moment I can confirm that authentication works correctly with:
- openid_connect:8.x-1.2
- https://git.drupalcode.org/issue/openid_connect_windows_aad-3021812/-/tr...
On the contrary at the moment beta versions do not work
- openid_connect:2.0.0-beta3
- openid_connect:beta-2.0.0-beta4
Translated with www.DeepL.com/Translator (free version)