[
https://issues.apache.org/jira/browse/NIFI-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17554607#comment-17554607
]
Mike R edited comment on NIFI-9849 at 6/15/22 1:44 PM:
-------------------------------------------------------
[~exceptionfactory] Thank you very much. A quick cursory search using mvn
dependency:tree on NiFi 1.16.3 source showed that these were almost all under
1.0.10, but you know better than I do and that was a quick search. Therefore,
if all the references to 1.0.10 are removed, then the dependency should remove
too. I think there might have been 1 place that the velocity-core might have
been used, but I will take the time to update it now.
was (Author: JIRAUSER287407):
[~exceptionfactory] Thank you very much. A quick cursory search using mvn
dependency:tree on NiFi 1.16.3 source showed that these were almost all under
1.0.10, but you know better than I do and that was a quick search. I think
there might have been 1 place that the velocity-core might have been used, but
I will take the time to update it now.
> Refactor SAML 2 Support using Spring Security 5
> -----------------------------------------------
>
> Key: NIFI-9849
> URL: https://issues.apache.org/jira/browse/NIFI-9849
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework, Security
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
>
> The [Spring Security SAML|https://spring.io/projects/spring-security-saml]
> project, which provides the implementation for SAML integration in NiFi
> reached end of life in October 2021. Spring Security 5.5 and 5.6 include a
> new implementation of support for SAML integration.
> NiFi integration with SAML should be refactored to remove the dependency on
> the unmaintained Spring Security SAML library. The new implementation should
> be built on Spring Security 5 libraries, which also includes a number of
> transitive dependency upgrades.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
