Hi, @shiv_yadav,
I've tested your code change and it works as expected now. Thanks much.
Let me know if you need any more info on this.
Keith
kfolsom → created an issue.
@Giuseppe87, regarding #133 📌 4.0.0-alpha1 release compatible with D10/Symfony6 Fixed , I submitted code to the SimpleSAMLphp project that is now part of the 2.1 release that will add primary keys to the SimpleSAMLphp_saml_LogoutStore and SimpleSAMLphp_tableVersion tables and thus eliminate the error. The SimpleSAMLphp update code will run upon your first SAML-based login and add the keys. Commit is at here.
Thanks @Berdir for the explanation that the READ-COMMITTED isolation level for the Drupal database connection isn't being compromised. That's my main concern, given that the default isolation of REPEATABLE READ has been reported to cause deadlocks on tables that can lead to site performance problems.
I'll add a comment to the SimpleSAMLphp issues thread about this in case the maintainers are able at some point to change the table keys.
Thanks again.
I'm in the same situation as @esch regarding #104. My org runs Drupal websites at Pantheon and I have a D10 site there that's now using the same set-up for D10, simpleSAMLphp_auth, and SimpleSAMLphp as listed in #104. I'm also seeing the same error regarding the READ-COMMITTED transaction isolation level.
Both of those tables have a unique key that does not allow NULL values, so I changed them to primary keys as a test. So far, I'm seeing no problems with my ability to authenticate to the site.
Does anyone see a reason not to request that the SimpleSAMLphp maintainers change these keys to primary for the 2.1 release?