-
-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
after apollo spring session upgrade with config class SpringSessionConfig, LDAP login error #4536
Comments
A temporary solution is exclude the bean(springSessionConversionService) for ldap profile with |
@klboke would you please help to take a look at this issue? |
@Jxiu Hi, Are you already using Spring Session prior to the upgrade? If so, the serialized exception is expected. Just need to clear the user's session information, or guide the user to clear the browser's cookies. |
yes, and i clear the user's session and login with No trace browser @klboke |
@nobodyiam I think we need to spell this out when we release new versions
|
i have find waht is error,because of the lack of LDAP mixin.please see this issue and commit. <dependency>
<groupId>org.springframework.security</groupId>
<artifactId>spring-security-bom</artifactId>
<version>5.7.3</version>
<type>pom</type>
<scope>import</scope>
</dependency> I have solved this problem locally。 |
@Jxiu I don't understand what you mean. The change to json serialization is to facilitate subsequent upgrades, because the serialization ID of spring-projects/spring-security is always changing. Other integration aspects are fine, we also use LDAP login for production, I verified this |
i use apacheds LDAP,the error is below.
|
if other ldap config has no problems,i will close this issue。 are you both agree? |
@Jxiu I noticed the problem, I'll take a look at it. By the way @vdisk-group can you help to see if there is a problem with the OIDC integration? |
* add tech-support-qq-4.png * Update README.md * Enhance the user experience in the scenario of submitting duplicate keys * Modify the key-value conflict exception prompt, adjust the code style * fix(apollo-portal): Fix a json serialization problem during LDAP integration #4536 * refactor(apollo-portal): Move spring-security-bom * Update pom.xml Co-authored-by: Jason Song <[email protected]>
Describe the bug
after apollo spring session upgrade with config class SpringSessionConfig(#4484), ladp login error. http 500.
Spring-session JSON deserializing error.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
http 500
Screenshots
Additional Details & Logs
The text was updated successfully, but these errors were encountered: