np problem, glad it helps :) -Andy
--
- 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 received this message because you are subscribed to the Google Groups "CAS
Commun
I just came across that config property as your message came in :)
Thanks for the explanation Ray, it makes sense now that the ORM is picking
up that property when initializing everything that I saw during debugging.
That did do the trick, thanks everyone!
On Wednesday, November 27, 2019 at 3:
Bobby,
There are properties here,
https://apereo.github.io/cas/6.1.x/configuration/Configuration-Properties-Common.html#database-settings
one of them is
# ${configurationKey}.autocommit=false
where configurationKey would be something like cas.authn.jdbc.blah[0] (I have
not configured database
Hi Andy,
Are you referring to the autocommit property of the connection or the
database?
I'm using a postgresql database that has autocommit=true by default.
However, while debugging CAS I noticed that
*getJdbcTemplate().getDataSource().getConnection().getAutoCommit()* returns
*false*.
Manual
Hi Bobby,
See if you can try autocommit=true, as suggeested by this here:
https://groups.google.com/a/apereo.org/forum/#!topic/cas-user/Kf-dB0b_OuQ
If that would helps or not...\
Cheers!
- Andy
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List
*UPDATE*
After digging into this further, with debugging and increased log levels,
it appears that the method is actually getting hit and issuing the update
command to the DB. However, the update is immediately rolled back so the
database status is unchanged.
This is the new log message that co
Andy,
I checked both the logs and the database and neither showed evidence of the
postAuthenticate() method actually being called. Here is my custom handler:
public class CustomAuthenticationHandler extends
QueryDatabaseAuthenticationHandler {
Logger LOGGER = LoggerFactory.getLogger(Custom
Hi Bobby,
> the *postAuthenticate() *method does not seem to be getting called at all
How did you verified that postAuthenticate does not get called? Did you use
some logs or you just try executing some post JDBC query and they didn't
get called?
Have you used the keyword *@Override* to make su
Hi Andy,
Thanks for taking the time to look at this.
I did implement a new custom handler by extending
*QueryDatabaseAuthenticationHandler.
*According to the logs, the new handler is being picked up by CAS and
successfully used. However, the *postAuthenticate() *method does not seem
to be gett
Hi Bobby,
I have searched around the CAS 6 documentation, seems like there are
nothing similar to your use case build in (Althoguh it is still quite
possible that such feature exist but I didn't find it). I guess custom
implementing might be an feasible idea.
If I am customizing to add last us
10 matches
Mail list logo
