# How-to-fix-400-login-error-after-upgrade-to-24.3_688988344
## Problem:

After upgrading to 24.3, you may encounter a "400" error when attempting to log in to the system.

## Root cause:

1. In default, the server http header max size of bo-login be stetted to 65536 using the setting "server.max-http-header-size".
2. Spring Boot 3.2 remove "server.max-http-header-size" and replace with "server.max-http-request-header-size".
3. "server.max-http-request-header-size" default size is 8192.
4. after 24.3, the bo-login will be using the default "server.max-http-request-header-size" max size = 8192.
5. So, if additional cookie appended in SMAX header, the header size will max than 8192. User can’t login to SMAX

## Solution:

Following these steps to add max-http-request-header-size parameter with correct header size:

- Login to master or bastion node.
- Run the command to check the JAVA\_OPTS for itom-bo-login-deployment

***kubectl get deploy itom-bo-login-deployment -n <itsma-namespace> -o json | grep JAVA\_OPTS -A 3 -B 1***

***Results:***

{

"name": "JAVA\_OPTS",

"value": "-Djava.security.egd= [file:/dev/./urandom](http://file/dev/urandom) "

}

- Run the command to update the JAVA\_OPTS env

***kubectl set env deploy/itom-bo-login-deployment JAVA\_OPTS="-Djava.security.egd= [file:/dev/./urandom](http://file/dev/urandom) -Dserver.max-http-request-header-size=65536" -c itom-bo-login -n <itsma-namespace>***

- Run the command to check the JAVA\_OPTS for itom-bo-login deployment again

***kubectl get deploy itom-bo-login-deployment -n <itsma-namespace> -o json | grep JAVA\_OPTS -A 3 -B 1***

***Results:***

  {

"name": "JAVA\_OPTS",

"value": "-Djava.security.egd= [file:/dev/./urandom](http://file/dev/urandom) -Dserver.max-http-request-header-size=65536"

}

- Then Waiting for itom-bo-login pod to start
