-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Spring Session JDBC JSON format invalid escape sequence #3299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
mindhaq
added a commit
to mindhaq/spring-session
that referenced
this issue
Jan 7, 2025
…ains a special character
mindhaq
added a commit
to mindhaq/spring-session
that referenced
this issue
Jan 7, 2025
… encode() to insert JSON byte stream into PreparedStatement. This works with session attributes containing special characters in the JSON blob.
rwinch
pushed a commit
to mindhaq/spring-session
that referenced
this issue
Apr 22, 2025
…ains a special character
rwinch
pushed a commit
to mindhaq/spring-session
that referenced
this issue
Apr 22, 2025
… encode() to insert JSON byte stream into PreparedStatement. This works with session attributes containing special characters in the JSON blob.
rwinch
pushed a commit
that referenced
this issue
Apr 22, 2025
rwinch
pushed a commit
that referenced
this issue
Apr 22, 2025
…sert JSON byte stream into PreparedStatement. This works with session attributes containing special characters in the JSON blob.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
I want to store spring security session via JDBC in a Postgres database, and followed those instructions.
When the stored principal has an Umlaut in its name attribute (e.g. "Rüdiger"), storing
SPRING_SECURITY_CONTEXT
fails with an error like this:To Reproduce
The SQL for inserting/updating session attributes does not seem to work with those characters.
To reproduce, try this SQL containing the encode part from the suggested SQL in the spring-session documentation:
Expected behavior
Storing non-ASCII characters in JSON fields should be possible.
Sample
Try the SQL above online here:
https://onecompiler.com/postgresql/4337htpct
The text was updated successfully, but these errors were encountered: