-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Client registration doesn't work when Spring Boot configured to use snake case #4164
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
riky2124
added a commit
to riky2124/spring-boot-admin
that referenced
this issue
Apr 21, 2025
hzpz
pushed a commit
to riky2124/spring-boot-admin
that referenced
this issue
Apr 25, 2025
hzpz
pushed a commit
to riky2124/spring-boot-admin
that referenced
this issue
Apr 25, 2025
hzpz
pushed a commit
to riky2124/spring-boot-admin
that referenced
this issue
May 2, 2025
This bug was introduced by #3930 and is released since 3.4.2, as a workaround 3.4.1 can be used meanwhile |
hzpz
pushed a commit
to riky2124/spring-boot-admin
that referenced
this issue
May 23, 2025
hzpz
pushed a commit
to riky2124/spring-boot-admin
that referenced
this issue
May 23, 2025
hzpz
added a commit
that referenced
this issue
May 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Spring Boot Admin Server information
Version:
Spring Boot Admin server & client 3.4.5
Spring Boot version:
Spring Boot 3.4
Configured Security:
basic auth, but not relevant to this issue
Webflux or Servlet application:
servlet, but not relevant to this issue
Client information
Spring Boot versions:
Spring Boot 3.4
Used discovery mechanism:
self registration
Webflux or Servlet application:
servlet, but not relevant to this issue
Description
When the client app uses the property
spring.jackson.property-naming-strategy: SNAKE_CASE
, then the registration client will write the body for the registration request using snake case.This can't be deserialized properly by RegistrationDeserializer as it supports only camel case.
I would expect Spring Boot Admin to not rely on the generic MessageConverters facility from Spring but instead configure explicitly the ObjectMapper.
## Reproducer
You can easily reproduce this issue with the test
ClientServletApplicationTest
by adding"--spring.jackson.property-naming-strategy=SNAKE_CASE"
to theapplication.run(...)
The text was updated successfully, but these errors were encountered: