This issue happens during upgrading 3.1 SP4 Access Manager to 3.2. To workaround this issue:
After upgrade, go to NMAS > NMAS Login Sequences and delete the SAML assertion.
Go to NMAS > NMAS Login Methods and delete the SAML assertion.