If SimpleSAMLPHP is configured using the default PHPSESSION option for session management, the 8.x module silently fails and redirects to the user.login path.

The module needs to present a warning message that this is the reason it has exited out of the SAML login process.

CommentFileSizeAuthor
#2 simplesamlphp_auth-storetype_warning-2897043-2-D8.patch640 bytesdiamondsea
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

diamondsea created an issue. See original summary.

diamondsea’s picture

diamondsea
he/him/his
Primary language English
CreditAttribution: diamondsea as a volunteer and at Publicis Sapient for Publicis Sapient commented
FileSize
simplesamlphp_auth-storetype_warning-2897043-2-D8.patch640 bytes

SImple patch to display warning. Should probably include hook_requirements() checks but this will at least help.

diamondsea’s picture

diamondsea
he/him/his
Primary language English
CreditAttribution: diamondsea as a volunteer and at Publicis Sapient for Publicis Sapient commented
Category: Bug report » Feature request
diamondsea’s picture

diamondsea
he/him/his
Primary language English
CreditAttribution: diamondsea as a volunteer and at Publicis Sapient for Publicis Sapient commented
Title: Notify if using PHPSESSION for session storage » /saml_login redirects to /user/login. Notify if using PHPSESSION for session storage
diamondsea’s picture

diamondsea
he/him/his
Primary language English
CreditAttribution: diamondsea as a volunteer and at Publicis Sapient for Publicis Sapient commented

Not sure if #754560: Messages are lost if set just prior to logout might affect this or not. Mentioning here for future reference.

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir commented
Status: Active » Needs review
Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir commented
Status: Needs review » Needs work

> SImple patch to display warning. Should probably include hook_requirements() checks but this will at least help.

I'd love to have a requirements check for that. Pretty sure that weird bugs like #2837029: All site forms fail with "The form has become outdated" after allowing "Authenticated user" role to log in with local accounts are actually a version of this.