[
https://issues.apache.org/jira/browse/SHIRO-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071038#comment-13071038
]
Jaakko Saari commented on SHIRO-305:
------------------------------------
There's a workaround if you can use spring integration. Configure your
securitymanager, realm etc beans in and set the environment variables as a map
property on the contextfactory bean.
> Connect to a SSL secured LDAP
> -----------------------------
>
> Key: SHIRO-305
> URL: https://issues.apache.org/jira/browse/SHIRO-305
> Project: Shiro
> Issue Type: Bug
> Components: Realms
> Affects Versions: 1.1.0
> Environment: Windows 7, Tomcat 6.x
> Reporter: Peter Diefenthäler
> Fix For: 1.1.1
>
>
> Configuration for connecting the Shiro framework with a SSL secured LDAP
> (LDAPv2 & LDAPv3 on SSLv3 port) fails.
> Parameters for LDAP in the shiro.ini file:
> [main]
> ...
> ldapRealm.contextFactory.environment[java.naming.security.protocol] = ssl
> ldapRealm.contextFactory.environment[com.sun.jndi.ldap.connect.pool.protocol]
> = plain ssl
> ldapRealm.contextFactory.environment[com.sun.jndi.ldap.connect.pool] = true
> These entries lead to following error message:
> org.apache.shiro.config.ConfigurationException: Map property value [ssl]
> contained key-value pair token [ssl] that does not properly split to a single
> key and pair. This must be the case for all map entries.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
