Do you mean it is buggy because Redis was refusing to write -1 for
expiration times?
If you have a lot of time I guess you could write your test case and
request pull.
Uxío Prego
Madiva Soluciones
CL / SERRANO GALVACHE 56
BLOQUE ABEDUL PLANTA 4
28033 MADRID
+34 917 56 84 94
www.madiva.com
Sorry, there's a bit of a history to the problem that involved several
other ticket registries.
On CAS 3.5 we where using PostgreSQL, but when I upgraded to CAS 5.x I
switched to Hazelcast. Which work okay except that after three days
pinciple ID's start to become null after successful
I’m a little lost now.
Are you sure you need to waste that much energy investigating so many ticket
registry alternatives? Shouldn’t you be trying to just assess the feasibility
of using that data base with which you feel more comfortable?
To be more clear, let’s say it works better using
So it turns out I already had the driver turned to debug, so no new
information there. But I did up the verbosity level of MongoDB log to 5
and noticed that a write attempt for the TGT ticket wasn't even made
(subsequent fetches where made though).
I decided to try pulling down the latest maven
Oh... Goodness. I was hoping the ORM software to be at last using BYTEA
instead of LO/OID.
Thank you, you are very much kind.
Uxío Prego
Madiva Soluciones
CL / SERRANO GALVACHE 56
BLOQUE ABEDUL PLANTA 4
28033 MADRID
+34 917 56 84 94
www.madiva.com
www.bbva.com
The activity of email inboxes
I'll give that a shot and let you know what I find.
Thank you.
On Wed, Feb 7, 2018 at 5:31 AM, David Curry
wrote:
> Ah - you just reminded me, and I should have mentioned this last time. Try
> adding this to your log4j2.xml:
>
>
>
>
> That's the actual Java driver.
Hi Uxio,
Sure I can share that. I had to do a few tweaks to the database. The first
is if you are using SAML, you need to change the samlobject columns from
varchar(5000) to text, because signed assertions will exceed those 5000
characters really fast.
Next you want to update the constraints
Ah - you just reminded me, and I should have mentioned this last time. Try
adding this to your log4j2.xml:
That's the actual Java driver.
--Dave
--
DAVID A. CURRY, CISSP
*DIRECTOR OF INFORMATION SECURITY*
INFORMATION TECHNOLOGY
71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003
+1 212 229-5300
Hi Dave,
I actually tried those settings first (I was following your guide, but only
having a single server instead of a cluster for mongo). Unfortunately, it
fails in the same way with those settings too. I might be able to eek out
a little more information if I set
Mike,
The only thing that strikes me as odd in your settings is this one:
cas.ticket.registry.mongo.collectionName=cas-ticket-registry
The Mongo ticket registry uses multiple collections:
proxyGrantingTicketsCollection
proxyTicketsCollection
samlArtifactsCache
samlAttributeQueryCache
assuming its not a time-out issue , then debug from source
El miércoles, 7 de febrero de 2018, Mike Kromarek
escribió:
> The title should read CAS 5.2.2 for the version
>
> --Mike K.
>
> On Wednesday, February 7, 2018 at 1:03:43 AM UTC-8, Mike Kromarek wrote:
>>
>> I
I'm sorry I can't help you, but it would be very sweet if you could share
your effective serviceticket or ticketgrantingticket table schema from the
times when you were using PostgrelSQL as ticket registry for CAS 5...
Regards,
Uxío Prego
Madiva Soluciones
CL / SERRANO GALVACHE 56
BLOQUE
12 matches
Mail list logo