Spring WS authentication doesn't work when using a PropertyPlaceHolderConfigurer object [SWS-429]

[gregturn]

Angel opened SWS-429 and commented

Hi.

My web service begins to fail when I change the SimplePasswordValidationCallbackHandler to get the password from a PropertyPlaceHolderConfigurer like this:

<bean id="simpleTokenValidationHandler"
	class="org.springframework.ws.soap.security.xwss.callback.SimplePasswordValidationCallbackHandler">
	<property name="users">
		<props>
			<prop key="user"><b>${ws.password}</b></prop>
		</props>
	</property>
</bean>

I know that it is resolving its value at start-up but the authentication fails and it shouldn't.

---

Affects: 1.5.4

Issue Links:

• WSDL is renedered without resolving dynamic attributes managed using a PropertyPlaceHolderConfigurer object [SWS-430] #575 WSDL is renedered without resolving dynamic attributes managed using a PropertyPlaceHolderConfigurer object

[gregturn]

Angel commented

Sorry, this is the bean definition that is failing

<bean id="simpleTokenValidationHandler"
	class="org.springframework.ws.soap.security.xwss.callback.SimplePasswordValidationCallbackHandler">
	<property name="users">
        <props>
            <prop key="DATA_HARVEST">${ws.password}</prop>
        </props>
    </property>
</bean>

[gregturn]

Arjen Poutsma commented

I can't think of a reason why this wouldn't work. Are you sure the properties are replaced at all?

You could try wiring up a simple pojo, wire it up with a property, and print out the property value as soon as injected. Just to be sure.

[gregturn]

Angel commented

Yes, I am completely sure. I think it is comparing against the literal "${ws.password}" instead of using the resolved value. I think the issue #575 could be related to this and the way property binding is managed.

[gregturn]

Arjen Poutsma commented

I cannot reproduce this. See #575 for a suggested fix.

[gregturn]

Arjen Poutsma commented

Closing old issues