Error encountered when accessing SAML authentication mapping configuration page

I'm getting the same issue. It looks like the solution Rishi Kulshreshtha created brings the page back.

I'm getting the same issue. It looks like the solution Rishi Kulshreshtha created brings the page back.

Also ran into this issue and can confirm the change in the linked merge request restores access to the page.

This is because of changes made to externalauth.

While I don't doubt that this works,

• I don't know why it works, so I don't know if it will keep working. ($row apparently has two separate properties with the same value. They used to be $row->authmap_uid and $row->users_field_data_authmap_uid. After the update to externalauth 2.0.4, the properties are $row->uid and $row->users_field_data_authmap_uid. OK, but why are there two? Maybe that knowledge will help solve the referenced externalauth issue too. Because it works for me... but... some people are apparently still having issues?)
• I want to keep the code in sync with externalauth. That means looking at the changes in 2.0.4 and possibly incorporating them. But I'm not sure having uid be the base_field makes sense there, given that it's not necessarily a unique value?

It may well be that the solution in this MR is the right one, but I want to doublecheck if the 'parent issue' can be closed, first (or at least, that it won't affect us).

If you want to fix the issue now: downgrade externalauth to 2.0.3. There are no changes since 2.0.3 except for the view (which my view is based on) and gitlab / phpcs.

MrKennedy → changed the visibility of the branch 3424834-error-encountered-when to hidden.

I have same problem with these versions samlauth: 8.x-3.9 & externalauth: 2.0.5 and that merge request !18 is solving my problem.

Probably should wait for the next release of externalauth and up the minimum requirement to that release. That way if you see this error and update samlauth, it'll update externalauth too.

Thanks, that's a good idea. There's no reason not to update that minimum requirement.

I'm still keeping this issue open, to think about (including the linked externalauth issue) when I have time.