I had a bad time trying to tweak CAS 3 with postgres ticket registry to use 
bytea for lobs, instead of oid, ended up using oid and assuming the included 
pita and believing there is a bug relating how hibernate 4 handles ticket 
removal when using postgres [oid] large objects (update/delete most possibly 
requiring multiple data unlinking ops just after commiting transaction).

If I were to want the supposed bug to be solved for CAS (not the case) I would 
open issue in CAS even thouh really sure it is (seems at least) an hibernate 
bug. The reason for it is that even there are more or less maintained public 
roadmaps often only someone in the team really knows the truth on the facts for 
the multiplicity of data access layer back ends.

CAS seems to have an historical affinity with particular versions of mysql and 
oracle to a lesser extent.

Targeting maria or not is mandatory for hibernate I would say (so that said, 
plans or mission statements are no guarantee for anything), but in the scope of 
CAS is something to be decided by the CAS committee.

I would open a github issue.

Sent from my iPhone

> On 16 Aug 2017, at 12:55, Matt Elson <mailing_lists....@melson.fastmail.net> 
> wrote:
> 
>> On 08/15/2017 04:47 PM, Matt Elson wrote:
>> 
>> Both look like the SQL statements are getting incorrectly formed or
>> truncated in some format; going to be firing up more debugging on
>> mariadb/mysql side of things and will try other DBs later.
>> 
>> Just figured I'd throw it out there in case the underlying cause of this
>> new issue of mine is a really obvious one.
> 
> Turns out it's pretty simple.
> 
> The fields "date" and "key" are reserved words in mysql/mariadb and
> aren't being quoted/backticked properly so causing the SQL errors.
> Changing the names to something like trustedDate and trustedKey in
> MultiFactorAuthenticationRecord  and altering the explicit SQL queries
> in JpaMultifactorAuthenticationTrustStorage accordingly causes the DDL
> and subsequent inserts to succeed in my brief testing.
> 
> While playing with that, a length of 255 isn't sufficient for the key
> value once encryption takes place; had to bump it up to 1000 or so.
> 
> Not familiar with hibernate so not sure if it's supposed to take care of
> this sort of quoting/escaping, so not sure who to report this seeming
> bug to.
> 
> Matt
> 
> -- 
> - CAS gitter chatroom: https://gitter.im/apereo/cas
> - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
> - CAS documentation website: https://apereo.github.io/cas
> - CAS project website: https://github.com/apereo/cas
> --- 
> You received this message because you are subscribed to the Google Groups 
> "CAS Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to cas-user+unsubscr...@apereo.org.
> To view this discussion on the web visit 
> https://groups.google.com/a/apereo.org/d/msgid/cas-user/458110c3-b065-e8a2-052f-140025781224%40fastmail.net.

-- 
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/4BDD2C52-C382-4DAE-BC84-E7D9DC73300B%40madiva.com.

Reply via email to