Strange difference in attribute name for client advanced SAML config dev vs production

I am developing an application that creates a client in a Keycloak 19.0.1 realm and has to set the ‘Logout Service POST Binding URL’ via the Java REST API. Following some advice I found, I used the Chrome developer tools to view the HTTP request sent when setting the value of this attribute via the admin console that is running in production mode on an AWS EC2 instance. From inspecting the request, I found the attribute name used was ‘post.logout.redirect.uris’. However, using this attribute didn’t work.

I set up Keycloak 19.0.1 in my local dev. environment to see if I could figure out what was going on. When I looked at the HTTP request on the local admin console. the attribute name was ‘saml_single_logout_service_url_post’. Using this attribute name in the API call worked both locally and on the EC2 instance.

So I have solved my issue but thought I would post this information in case it’s useful.