Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I've faced with error during execute drush command on server:
Drush command terminated abnormally due to an unrecoverable error. [error]
SimpleSAML_Error_Exception: Setting secure cookie on plain HTTP is not allowed. in SimpleSAML_Session::getSessionFromRequest() (line 287 of sites/all/libraries/simplesamlphp/lib/SimpleSAML/Session.php).
Comments
Comment #2
kiseleva.t CreditAttribution: kiseleva.t as a volunteer and at DrupalJedi commentedThis patch solved issue for me.
Comment #3
kiseleva.t CreditAttribution: kiseleva.t as a volunteer and at DrupalJedi commentedUpdated patch from 7.x-2.x-dev version and changed order of check.
Comment #4
kiseleva.t CreditAttribution: kiseleva.t as a volunteer and at DrupalJedi commentedComment #5
kiseleva.t CreditAttribution: kiseleva.t as a volunteer and at DrupalJedi commentedPatch from comment 3 has wrong place check, fixed.
Comment #7
snufkin CreditAttribution: snufkin as a volunteer commentedLooks like an obvious fix to the problem, I'm surprised this hasn't come up before :) Thanks!
Comment #8
snufkin CreditAttribution: snufkin as a volunteer commentedPorting the patch for 7.x-3.x. Should be trivial.
Comment #9
aprohl5 CreditAttribution: aprohl5 as a volunteer commentedI am unable to reproduce this issue in the current 7.x-3.x-dev version of the module despite the patches above appearing to have been unapplied. is there a specific command that was erroring out in order to produce this issue?
Comment #10
a_thakur CreditAttribution: a_thakur as a volunteer and at Srijan | A Material+ Company commentedI ran into a similar problem where I had to create a new user in update hook, due to hook_user_insert implementation in 2.x fails, does it make sense to add a similar condition there as well?
Comment #11
kiseleva.t CreditAttribution: kiseleva.t as a volunteer and at DrupalJedi commentedFor me issue appeared during automatic deployment on stage server, I think it could be drush updb or something like that.
Also it happened only when I enabled session.cookie.secure in config, before I didn't have such error.
Comment #12
brianfisher CreditAttribution: brianfisher at Chapter Three commentedFor those on 7.x-2.x, this patch fixes comment #10