You should probably start by reading the CAS SAML documentation:
https://apereo.github.io/cas/development/installation/Configuring-SAML2-Authentication.html
And then you can look at, for example, the instructions here:
https://dacurry-tns.github.io/deploying-apereo-cas/introduction_overview.html
Hi Alex,
Error code 49 is wrong username / password.
Can you bind from the command line ok with the DN and password below using
ldapsearch or similar?
Should it be ou=Users in the DN instead of cn=Users? The xxx in cn=xxx should
be your username not your domain name.
Lastly, y
Hi Mohannad,
I just follow your setting and make myself a quick 1 hour demo. And I do
make it working.
In the process I spotted something weird in your setting.
Can you try moving the entire src folder inside the cas folder, just like
how this person did:
https://github.com/ijunjie/my-cas-ov
Yes -- it was already set --- properties below.
However, I was less than accurate in my initial post.
The CAS.WAR and CAS-MANAGEMENT.WAR are running in same Tomcat. The Tomcat
is listening on port 8080; there is an Apache listening at 443 that proxies
traffic to the Tomcat.
Is the CAS-MANAGEME
Hi,
I would like to use X509 authentication with CAS REST API (as described
here: https://apereo.github.io/cas/5.2.x/protocol/REST-Protocol.html). I'm
surprised that there is a certificate parameter to the request, as I
thought the certificate should be taken from the servlet container
environ
Hi Andy,
Actually this line cas.javascript.file=/themes/hbmsu/js/cas.js is commented
in my properties file that's why I did not create the JS folder. Anyway I
added the JS folder and uncommented that line and tried again and it gave
the same error.
Do I need to enable any extra dependency or c
Presently, we are using CAS as an Identity Provider but now we want to use
SAML2.0 as an Identity provider instead of CAS server. As I'm new to CAS,
can anyone help me out the steps that I need to follow? and I have some
queries like, Do we need to configure the SAML Request & Response
externally?
Hi,
I'm glad to see that you confirm the bug. I'll try to make a Pull Request,
but I need to setup a full CAS dev env before.
Regards,
Charles
Le mercredi 23 mai 2018 18:59:17 UTC+2, Christian Poirier a écrit :
>
> I think I know what you mean by "is buggy". I check the code and it misses
>
cas.authn.ldap[0].type=AUTHENTICATED
cas.authn.ldap[0].ldapUrl=ldap://ldap.staff.tigerbrokers.com:389
cas.authn.ldap[0].useSsl=false
cas.authn.ldap[0].baseDn=dc=staff,dc=tigerbrokers,dc=com
cas.authn.ldap[0].searchFilter=sAMAccountName={user}
cas.authn.ldap[0].bindDn=cn=xx,cn=Users,dc=staff,dc=
