Skip to content

Conversation

@Zonnex
Copy link
Contributor

@Zonnex Zonnex commented Oct 8, 2025

This PR fixes #516.

As per the issue linked, sometimes we send returnUrls to BankId that are invalid, one case seem to be that the returnUrl is too long which in our internal testing resulted in cryptic error, but others have received "Invalid Parameter". We couldn't replicate this directly but it's definitely a problem if the uiOptions are too long, which is also ugly.

Later we have a solution for those who wish to store data somewhere else but to fix issue we went with this approach for now, that we store the UIOptions in a cookie and pass a guid in the returnUrl instead. I have not had time to test this thoroughly so that's remaining.

@Zonnex Zonnex requested a review from elinohlsson October 8, 2025 06:17
@Zonnex Zonnex force-pushed the fix/479-returnUrl branch from 82ed682 to f332f67 Compare October 8, 2025 06:28
@elinohlsson elinohlsson merged commit 8a49118 into main Oct 9, 2025
18 checks passed
@elinohlsson elinohlsson deleted the fix/479-returnUrl branch October 9, 2025 13:08
@elinohlsson elinohlsson added this to the Next Release milestone Oct 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Auth errors after upgrading to v11.1.0 - "Invalid returnUrl"

3 participants