We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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:
SPRING_SECURITY_CONTEXT
[22P02] ERROR: invalid input syntax for type json Detail: Escape sequence "\3" is invalid. Where: JSON data, line 1: {"name":"R\3...
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:
SELECT encode('{"name":"Rüdiger"}', 'escape')::jsonb;
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:
spring-projects#3299: adjust test so that it fails when username cont…
f4cd1d0
…ains a special character
spring-projects#3299: use postgres function convert_from() instead of…
8e86689
… encode() to insert JSON byte stream into PreparedStatement. This works with session attributes containing special characters in the JSON blob.
Successfully merging a pull request may close this issue.
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: