Answer
Check whether a companion release was required alongside the one you applied but wasn't clearly flagged as a dependency — in one confirmed case, this exact login-breaking authentication error was caused by a missing release that IFS hadn't communicated as a prerequisite; installing that additional release alongside the one already applied resolved the login failure completely. If a delivery/SU install otherwise looks completely clean (no installation errors, all services green) but breaks authentication specifically, a missing dependent release is worth checking for before assuming a deeper configuration problem.