- Issue created by @Johan den Hollander
- 🇳🇱Netherlands roderickgadellaabsl
We ran into this issue as well. It seems like existing sessions that were created using saml2 <= 4.6.10 can not be parsed by 4.6.11. We used the mysql option to store sessions. A TRUNCATE of the tables fixed it for us.
(Note: also truncate the Drupal `sessions` table or you end up in an endless redirect loop)
```
--- SimpleSAMLphp database:
TRUNCATE SimpleSAMLphp_kvstore;
TRUNCATE SimpleSAMLphp_saml_LogoutStore;--- Drupal database:
TRUNCATE sessions;
``` - 🇨🇭Switzerland berdir Switzerland
That sounds like a SimpleSAMLphp bug that we can't do anything about.
- 🇳🇱Netherlands Johan den Hollander
Thanks @roderickgadellaabsl this seems like a easy way to solve it.
Will try this with the next release cycle of the website we were having the problem with.Although there is nothing that needs fixing in this module, we can leave this here for other people to find it!
- 🇳🇱Netherlands idebr
Solution #2 in code:
drush sql-query "TRUNCATE TABLE sessions" drush sql-query "TRUNCATE TABLE simpleSAMLphp_kvstore" drush sql-query "TRUNCATE TABLE simpleSAMLphp_saml_LogoutStore"
Hello,
I'm experiencing the same.
SimpleSamlphp is installed with composer as part DrupalI looked at my databases/tables:
I do not have a " SimpleSAMLphp" database.
and do not have "simpleSAMLphp_kvstore" and "simpleSAMLphp_saml_LogoutStore" tableshowever in the Drupal database, I do have:
simplesaml_saml_LogoutStore and
simpleSAMLphp_saml_LogoutStoreAm I missing something?
- 🇳🇱Netherlands roderickgadellaabsl
I do not have a " SimpleSAMLphp" database.
The tables are (probably) in your Drupal database, not a separate one.