exceptionfactory opened a new pull request, #6145: URL: https://github.com/apache/nifi/pull/6145
# Summary [NIFI-9849](https://issues.apache.org/jira/browse/NIFI-9849) Refactors SAML 2.0 authentication support using Spring Security 5 libraries. The `spring-security-saml2-core` library reached [end of life in October 2021](https://spring.io/blog/2020/09/22/spring-security-saml-extensions-1-x-eol-on-october-6-2021). Spring Security 5 introduced direct support for SAML 2.0 integration through the `spring-security-saml2-service-provider` library. The refactored implementation replaces custom REST resources with Spring Security Filters and related components. The new `Saml2AccessResource` class has a single method for returning a Bearer Token previously set as cookie following successful SAML 2.0 authentication. The updated approach maintains support for existing SAML resource paths, and the Administrator's Guide includes an additional section for supported resources. The new implementation retains support for existing SAML application properties, with the exception of the following removed properties: 1. `nifi.security.user.saml.message.logging.enabled` 2. `nifi.security.user.saml.metadata.signing.enabled` 3. `nifi.security.user.saml.signature.digest.algorithm` The `message.logging.enabled` property is no longer applicable to the refactored implementation, and standard logger configuration applies to various Spring Security components. The `metadata.signing.enabled` and `signature.digest.algorithm` properties applied signing SAML metadata and do not have analogous options in Spring Security 5. The Spring Security 5 library supports both OpenSAML 3 and OpenSAML 4, however, OpenSAML 4 requires Java 11. Spring Security has marked OpenSAML 3 components as deprecated, and these implementations will need to be replaced with OpenSAML 4 components when Apache NiFi removes support for Java 8. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [X] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [X] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-00000` - [X] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000` ### Pull Request Formatting - [X] Pull Request based on current revision of the `main` branch - [X] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [X] Build completed using `mvn clean install -P contrib-check` - [X] JDK 8 - [X] JDK 11 - [X] JDK 17 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [X] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
