Closed codepari closed 8 months ago
Hi, how did you get to this lead? Did you see this error message in your logs?
I assume if Base64.getUrlDecoder().decode(signature) throws a BadPaddingException, this would be the case.
Did you try to validate the signature of the token in a different tool, e.g. https://jwt.io/? How did you get this token? Is it a real XSUAA token issued when logging in? Do you see this message when you enable debug logging for our library?
Closing this as Github Issue section is no longer maintained.
We are migrating our apps from spring-xsuaa to spring-security by following the guides published here:
Spring Security guide: https://github.com/SAP/cloud-security-services-integration-library/tree/main/spring-security
Migration guide: https://github.com/SAP/cloud-security-services-integration-library/blob/main/spring-security/Migration_SpringXsuaaProjects.md
Feature branch: https://github.tools.sap/LBN/lbn-freightOrdersForSettlement/tree/Spring3Java17_V2/lbn-freightOrdersForSettlement-service
=========== We got some lead, the issue was occurring due to the size of the JWT token.
JwtSignatureValidator => Base64.getUrlDecoder().decode(signature)
sun.security.jca.JCAUtil.RSAPadding => BadPaddingException was coming Please let us know how to resolve this??