[Improve]Optimize the way of obtaining user information.

[zhangshenghang]

Purpose of this pull request

In the Spring project, the user ID should not be passed in through the front end, but the general Servlet should be used to obtain user information.

Check list

• Code changed are covered with tests, or it does not need tests for reason:
• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs

[zhangshenghang]

@Hisoka-X PTAL

[Hisoka-X]

cc @arshadmohammad

[shashwatsai]

@zhangshenghang this makes a lot of sense, but isn't it possible to leverage spring-boot-starter-security and use SecurityContextHolder?

[arshadmohammad]

can you make these parameters configurable.

[zhangshenghang]

can you make these parameters configurable.

ok

[arshadmohammad]

I noticed that you have added async-config, but it is not being used in this code. Could you please verify this? Additionally, ensure that if the async-config entry is missing from the configuration, the default values are used.

[arshadmohammad]

@zhangshenghang can you please handle this

[arshadmohammad]

Nice improvement, Thanks @zhangshenghang

[zhangshenghang]

@zhangshenghang this makes a lot of sense, but isn't it possible to leverage spring-boot-starter-security and use SecurityContextHolder?

@shashwatsai Yes, currently the project does not use spring-boot-starter-security, it can be optimized separately.

[zhangshenghang]

@arshadmohammad @Hisoka-X PTAL

[arshadmohammad]

executor.setCorePoolSize(10); executor.setMaxPoolSize(20); executor.setQueueCapacity(100);
The AsyncConfig class is currently using hard-coded values instead of utilizing the configuration settings. @zhangshenghang can you handle this?

[zhangshenghang]

executor.setCorePoolSize(10); executor.setMaxPoolSize(20); executor.setQueueCapacity(100); The AsyncConfig class is currently using hard-coded values instead of utilizing the configuration settings. @zhangshenghang can you handle this?

OK. I forgot to submit it. It has been revised.

[zhangshenghang]

@arshadmohammad @Hisoka-X PTAL

[arshadmohammad]

Many integration tests are failing
[ERROR] UserControllerTest.login_shouldFail_whenInvalidAuthType:139 » Runtime
[ERROR] UserControllerTest.login_shouldPass_whenNoAuthType:124 » Runtime
[ERROR] UserControllerTest.login_shouldPass_whenValidAuthType:109 » Runtime
[ERROR] UserControllerTest.tearDown:184 » Runtime
[ERROR] UserControllerTest.updateUser_shouldReturnSuccess_whenValidRequest:73 » Runtime
[INFO]
[ERROR] Tests run: 48, Failures: 0, Errors: 48, Skipped: 0
[INFO]
[ERROR] There are test failures.

@zhangshenghang can you please run the integration tests and handle the failure.

[arshadmohammad]

Apologies for the confusion. After upgrading my existing Seatunnel database by executing the script below, the test cases have now passed.

ALTER TABLE user ADD COLUMN auth_provider varchar(10) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL DEFAULT 'DB';