Skip to content

Feat/split java security core - #2032

Open
NiklasHerrmann21 wants to merge 3 commits into
mainfrom
feat/split-java-security-core
Open

NiklasHerrmann21 wants to merge 3 commits into
mainfrom
feat/split-java-security-core

Conversation

@NiklasHerrmann21

Copy link
Copy Markdown
Contributor

No description provided.

…x509

Move the Jakarta-free core of java-security into its own module so that
token validation can be used from non-Jakarta environments (e.g. Tomcat 9 /
javax.servlet runtimes) and from non-servlet code:

- com.sap.cloud.security.token (token model, SecurityContext, TokenExchangeMode)
- com.sap.cloud.security.token.validation (+ all validators, JwtValidatorBuilder)
- com.sap.cloud.security.x509
- HybridTokenFactory + the TokenFactory ServiceLoader registration (pure Java
  despite the historical servlet package; required by Token.create())

Sources and tests are moved unchanged (git mv). The new module has no
jakarta.servlet and no Spring dependency.
- Add java-security-core to the root reactor
- Add java-security-core to the java-bom dependency management
- java-security now depends on java-security-core (kept classes reference
  the moved ones); existing consumers get the moved classes transitively,
  so this is backward compatible (minor release)
- Root README: note that javax/Tomcat 9 environments should use
  java-security-core (no jakarta.servlet, no Spring)
- java-security README: "The core part" section explaining what moved
  and that the FQNs are unchanged; fix source links to the moved classes
- CHANGELOG: 4.2.0 section describing the split and compatibility
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants