You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 the application.run(...)
The text was updated successfully, but these errors were encountered:
obourgain
changed the title
Client lob doesn't work when Spring Boot configured to use snake case
Client registration doesn't work when Spring Boot configured to use snake case
Mar 31, 2025
riky2124
added a commit
to riky2124/spring-boot-admin
that referenced
this issue
Apr 21, 2025
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: