Hey Neetika,
I wouldn't remove that check. It's there for security, so nobody can reuse an old login.
Here's what I'd check:
Turn on debug logs for SAML_SSO and see which values are clashing. If they're empty, it's a bug in the module, not a real duplicate.
If you run more than one instance or have a proxy that retries, the same login can get processed twice.
Look for a newer SAML module version, or raise a Mendix support ticket with your logs.
If you share the error, I can take a look 🙂
Hi Neetika,
If you're experiencing issues with concurrent users, please create a ticket at Mendix support.
Concurrent usage should work without problems.
We would be very interested to receive error details from logs etc to analyze the situation.
Hi Neetika ,
1. First try a clean login
2. Check whether the SAML callback is being called twice
3. Check your Identity Provider configuration
4. Check reverse proxy / load balancer behavior
5. Don't remove the AssertionId uniqueness/validation
follow this step & check it , if not the raise a support ticket to mendix
Thanks ,
Sujat
Hi Neetika,
The AssertionId uniqueness validation should not be disabled, as it is important for preventing SAML assertion replay attacks.
However, two users logging in simultaneously should not normally cause a uniqueness conflict, because each authentication response should contain a unique assertion ID.
I recommend the following troubleshooting steps:
1. Verify the actual Assertion IDs
Enable detailed logging temporarily in a non-production environment and reproduce the issue with two different users.
Compare the assertion IDs received from your Identity Provider (IdP).
Different Assertion IDs: The issue may be related to how the SAML module stores or processes concurrent authentication requests.
Identical Assertion IDs: Investigate why the IdP is returning the same assertion for multiple login attempts or whether the same SAML response is being submitted more than once.
2. Check for duplicate SAML response processing
Inspect the browser Network tab and application logs to determine whether /SSO/assertion is being called multiple times with the same response.
Also check for automatic login redirects, repeated callbacks, or custom authentication logic that could cause the same assertion to be processed twice.
3. Check the SAML request records
Review the SAML request records through the module's administration functionality, if logging is enabled.
Check whether the conflicting AssertionId already exists and whether it belongs to a previous authentication attempt.
4. Verify the SAML module configuration
Since SAML 4.2.4 introduced security-related fixes, ensure that the module upgrade and its required dependencies were completed correctly.
Also verify whether the issue occurs with a single runtime instance or only when multiple instances are running.
5. Check the complete exception
If both users receive different assertion IDs but the uniqueness validation still fails, capture the complete runtime stack trace and raise a Mendix Support ticket with a reproducible example.
This could indicate an issue in the assertion persistence or concurrent request handling, but the exact cause cannot be confirmed without the logs.
Important: Do not remove the unique constraint, disable assertion validation, or downgrade to a vulnerable SAML version as a workaround.
Official documentation:
Hope this helps! If you find this answer helpful, please mark it as the accepted answer.