The problem solved! with remove cas-server-support-ldap-service-registry
from pom.xml
On Thursday, July 30, 2020 at 11:53:00 PM UTC+4:30 mohsen saeedi wrote:
> I think i added cas-server-support-ldap-service-registry as dependency.
> and i don't have any configuration parameter for that on cas.
I think i added cas-server-support-ldap-service-registry as dependency. and
i don't have any configuration parameter for that on cas.properties. maybe
the problem caused for that!!! I will test again and send result here
On Thursday, July 30, 2020 at 9:03:25 PM UTC+4:30 mohsen saeedi wrote:
> T
The problem occur when it try to connect to ldap and finally failed to
start. for example i defined 192.168.250.71 as ldapUrl but it try to
connect to localhost!
Jul 30 20:58:38 SSO1 server[10311]: 2020-07-30 20:58:38,797 DEBUG
[org.apereo.cas.util.LdapUtils] - ldap://localhost:389]>
Jul 30 20
On Thu, Jul 30, 2020 at 3:23 AM mohsen saeedi
wrote:
> Jul 30 11:24:40 SSO1 server[4213]: 2020-07-30 11:24:40,315 ERROR
> [org.ldaptive.pool.BlockingConnectionPool]
>
What error is reported here?
--Daniel Fisher
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/a
Hi
I have experience more than 7 years on apereo CAS. after we updated our cas
overlay version to 5.2.3 (test with 5.3.6 too) one problem occur during
tomcat starting.
We define ldapUrl, bindDn, bindCredential in cas configuration file. this
config was working for older build (with 5.2.2 versio
