2024-08-09 19:26:09,136 - - WARN [org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker:437] - Bean 'org.opensaml.saml.metadata.resolver.filter.impl.EntitiesDescriptorNameProcessor#0' of type [org.opensaml.saml.metadata.resolver.filter.impl.EntitiesDescriptorNameProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [net.shibboleth.spring.metadata.NodeProcessingAttachingBeanPostProcessor#0]? Check the corresponding BeanPostProcessor declaration and its dependencies. 2024-08-09 19:26:09,137 - - WARN [org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker:437] - Bean 'net.shibboleth.idp.saml.security.impl.KeyAuthorityNodeProcessor#0' of type [net.shibboleth.idp.saml.security.impl.KeyAuthorityNodeProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [net.shibboleth.spring.metadata.NodeProcessingAttachingBeanPostProcessor#0]? Check the corresponding BeanPostProcessor declaration and its dependencies. 2024-08-09 19:26:09,140 - - WARN [org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker:437] - Bean 'net.shibboleth.idp.saml.metadata.impl.ScopesNodeProcessor#0' of type [net.shibboleth.idp.saml.metadata.impl.ScopesNodeProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [net.shibboleth.spring.metadata.NodeProcessingAttachingBeanPostProcessor#0]? Check the corresponding BeanPostProcessor declaration and its dependencies. 2024-08-09 19:26:09,141 - - WARN [org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker:437] - Bean 'net.shibboleth.idp.saml.metadata.impl.UIInfoNodeProcessor#0' of type [net.shibboleth.idp.saml.metadata.impl.UIInfoNodeProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [net.shibboleth.spring.metadata.NodeProcessingAttachingBeanPostProcessor#0]? Check the corresponding BeanPostProcessor declaration and its dependencies. 2024-08-09 19:26:09,145 - - WARN [org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker:437] - Bean 'net.shibboleth.idp.saml.attribute.impl.AttributeMappingNodeProcessor#0' of type [net.shibboleth.idp.saml.attribute.impl.AttributeMappingNodeProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected into a currently created BeanPostProcessor [net.shibboleth.spring.metadata.NodeProcessingAttachingBeanPostProcessor#0]? Check the corresponding BeanPostProcessor declaration and its dependencies. 2024-08-09 19:26:11,105 - - WARN [DEPRECATED:123] - Spring bean 'Liberty.SSOS or Liberty.SSOS.MDDriven', (relying-party.xml): This will be removed in the next major version of this software; replacement is (none) 2024-08-09 19:26:56,062 - 0:0:0:0:0:0:0:1 - WARN [net.shibboleth.idp.saml.profile.impl.PopulateBindingAndEndpointContexts:449] - Profile Action PopulateBindingAndEndpointContexts: Unable to resolve outbound message endpoint for relying party 'http://ipau.sp.sso.manager/sso': EndpointCriterion [type={urn:oasis:names:tc:SAML:2.0:metadata}AssertionConsumerService, Binding=urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST, Location=http://localhost:8080/SSOSPManager/SSO, trusted=false] 2024-08-09 19:26:56,072 - 0:0:0:0:0:0:0:1 - WARN [org.opensaml.profile.action.impl.LogEvent:94] - A non-proceed event occurred while processing the request: EndpointResolutionFailed