I don't use the jdbc attribute resolver, but the concept is similar to
others. What is your user table schema? You are doing a 'select *', rather
than explicitly listing the columns. Is there a column named firstname? You
are expecting to map a retrieved attribute named 'firstname' to a principal
my *cas.properties*:
## Database Authentication
##
cas.authn.accept.users=
cas.authn.jdbc.query[0].sql = SELECT * FROM users WHERE email=?
cas.authn.jdbc.query[0].healthQuery = SELECT 1
cas.authn.jdbc.query[0].driverClass =
Hi,
Continued with attribute problems.
*cas.properties*
cas.authn.attributeRepository.jdbc[0].sql = SELECT * FROM user_attributes
WHERE {$
cas.authn.attributeRepository.jdbc[0].healthQuery = SELECT 1
cas.authn.attributeRepository.jdbc[0].driverClass = com.mysql.jdbc.Driver
On 2 October 2018 at 01:16, Fahmi L. Ramdhani
wrote:
> Thanks dhawes,
> I have a little trouble about this, even though it should be able to. I
> configure it according to the documentation about attributes. Below are logs
> from mod_auth_cas:
The log excerpt looks like it was after validation.
Fahmi,
Put this in your CAS server log file to be sure that the attributes are being
released:
Ray
On Mon, 2018-10-01 at 22:16 -0700, Fahmi L. Ramdhani wrote:
Thanks dhawes,
I have a little trouble about this, even though it should be able to. I
configure it according to
Thanks dhawes,
I have a little trouble about this, even though it should be able to. I
configure it according to the documentation about attributes. Below are
logs from mod_auth_cas:
[Tue Oct 02 05:03:25.025216 2018] [:debug] [pid 21981] mod_auth_cas.c(1753):
[client 32.254.11.127:65177]
I use the mysql database. The point is that the attributes in the database
are displayed. Or do I have to use SAML?
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You
