Filtering Ldap Authentication Handler

Umut Arus umuta at sabanciuniv.edu
Thu Jun 28 03:15:45 EDT 2007


Yes, I had tested as you have typed. I think, syntax is (&) not 
accepted. Is there other syntax method?
After changing gives below error on authentication page,


    CAS is Unavailable

There was a fatal error initializing the CAS application context. This 
is almost always because of an error in the Spring bean configuration 
files. Are the files valid XML? Do the beans they refer to all exist?

Before placing CAS in production, you should change this page to present 
a UI appropriate for the case where the CAS web application is 
fundamentally broken. Perhaps "Sorry, CAS is currently unavailable." 
with some links to your user support information.

The Throwable encountered at context listener initialization was:

org.springframework.beans.factory.BeanDefinitionStoreException: Line 95 
in XML document from ServletContext resource 
[/WEB-INF/deployerConfigContext.xml] is invalid; nested exception is 
org.xml.sax.SAXParseException: The entity name must immediately follow 
the '*&*' in the entity reference.

The Throwable encountered at dispatcher servlet initialization was:

org.springframework.beans.factory.BeanDefinitionStoreException: Line 95 
in XML document from ServletContext resource 
[/WEB-INF/deployerConfigContext.xml] is invalid; nested exception is 
org.xml.sax.SAXParseException: The entity name must immediately follow 
the '&' in the entity reference.


Have you any suggestion?

Regards,


Marvin S. Addison wrote:

>>How can I add one more filter for ldap attribute of allowed users?
>>    
>>
>
>Something like the following should work:
>
><property name="filter" value="(&(uid=%u)(objectClass=user))" />
>
>Hope that helps,
>Marvin Addison
>  
>


-- 
Umut ARUS

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20070628/39dbfd18/attachment.html 


More information about the cas mailing list