[java-identity-provider] branch main updated: Failed to remove "legacy" deprecated flow.

Scott Cantor cantor.2 at osu.edu
Wed Feb 26 14:41:50 UTC 2025


This is an automated email from the git hooks/post-receive script.

scantor pushed a commit to branch main
in repository java-identity-provider.

View the commit online:
http://git.shibboleth.net/view/?p=java-identity-provider.git;a=commit;h=2bd2a3de07256b31208beba9a95504520958d3c6

The following commit(s) were added to refs/heads/main by this push:
     new 2bd2a3de0 Failed to remove "legacy" deprecated flow.
2bd2a3de0 is described below

commit 2bd2a3de07256b31208beba9a95504520958d3c6
Author: Scott Cantor <cantor.2 at osu.edu>
AuthorDate: Wed Feb 26 09:41:47 2025 -0500

    Failed to remove "legacy" deprecated flow.
---
 .../src/main/resources/net/shibboleth/idp/conf/webflow-config.xml        | 1 -
 1 file changed, 1 deletion(-)

diff --git a/idp-conf-impl/src/main/resources/net/shibboleth/idp/conf/webflow-config.xml b/idp-conf-impl/src/main/resources/net/shibboleth/idp/conf/webflow-config.xml
index 9f4d9249c..8f0935180 100644
--- a/idp-conf-impl/src/main/resources/net/shibboleth/idp/conf/webflow-config.xml
+++ b/idp-conf-impl/src/main/resources/net/shibboleth/idp/conf/webflow-config.xml
@@ -114,7 +114,6 @@
                 <entry key="c14n/SAML1Transient" value="classpath:/net/shibboleth/idp/flows/c14n/subject-c14n-saml-default-flow.xml" />
                 <entry key="c14n/SAML1CryptoTransient" value="classpath:/net/shibboleth/idp/flows/c14n/subject-c14n-saml-default-flow.xml" />
                 <entry key="c14n/SAML1Transform" value="classpath:/net/shibboleth/idp/flows/c14n/subject-c14n-saml-default-flow.xml" />
-                <entry key="c14n/LegacyPrincipalConnector" value="classpath:/net/shibboleth/idp/flows/c14n/subject-c14n-saml-default-flow.xml" />
         
                 <!-- Main interceptor flow. -->
                 <entry key="intercept.events" value="%{idp.home}/conf/intercept/intercept-events-flow.xml" />

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.


More information about the commits mailing list