Thanks - I found a "dirty" workaround by putting a password in plain text
in:
./tomcat/webapps/kylin/WEB-INF/classes/kylinSecurity.xml

like this:
                <bean id="ldapSource"
class="org.springframework.security.ldap.DefaultSpringSecurityContextSource">
                       <constructor-arg value="${ldap.server}" />
                       <property name="userDn" value="${ldap.user}" />
                       <property name="password" value="passhere" />
               </bean>


But that's a nasty hack...
M.

2015-12-10 8:51 GMT+01:00 Li Yang <[email protected]>:
>
> Shaofeng may comment... I only know how LDAP works not how it breaks...
>
> On Wed, Dec 9, 2015 at 9:03 PM, Marek Wiewiorka <[email protected]>
wrote:
>>
>> Hi All,
>> we are trying to setup LDAP connection and keep on getting the following
exception after doing base64 encoding:
>>
>> SEVERE: Exception sending context initialized event to listener instance
of class org.springframework.web.context.ContextLoaderListener
>> org.springframework.beans.factory.BeanDefinitionStoreException: Invalid
bean definition with name 'ldapSource' defined in class path resource
[kylinSecurity.xml]: Given fin
>> al block not properly padded
>>        at
org.springframework.beans.factory.config.PlaceholderConfigurerSupport.doProcessProperties(PlaceholderConfigurerSupport.java:209)
>>        at
org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.processProperties(PropertyPlaceholderConfigurer.java:220)
>>        at
org.springframework.beans.factory.config.PropertyResourceConfigurer.postProcessBeanFactory(PropertyResourceConfigurer.java:84)
>>        at
org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:686)
>>        at
org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:661)
>>        at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:451)
>>        at
org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383)
>>        at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283)
>>        at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111)
>>        at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5016)
>>        at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5524)
>>        at
org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>>        at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
>>        at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
>>        at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
>>        at
org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1081)
>>        at
org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1877)
>>        at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>>        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>>        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>        at java.lang.Thread.run(Thread.java:745)
>>
>> Do you have any idea what might be wrong?
>>
>> Thanks,
>> Marek
>>
>

Reply via email to