Shibboleth IdP 3.2.1 and Postgres as attribute source and queryTimeout

Cantor, Scott cantor.2 at
Mon May 23 16:35:24 EDT 2016

>   "Note to PostgreSQL users
> You have to set the "queryTimeout" attribute to "0". This feature is not yet
> supported by the PostgreSQL JDBC driver and the default value will cause a
> crash when starting the IdP."

Is that still true? I don't think it would be terribly safe to run an IdP with no timeout...

> And the docs for IdP v3 RelationalDatabase data connector have that
> queryTmeout parameter documented, either requiring a duration or
> milliseconds. But if I try to set 'queryTimeout="0"' for IdPv3, I get the
> following startup error which seems to indicate it will only accept a duration.
> Has anyone set up a Postgres attribute source and know the right setting to
> disable it trying to do a setQueryTimeput?

I had a bug open to figure out where we broke support for numeric values if we did, but did you try PT0?

-- Scott

More information about the users mailing list