All work
- Re-introduction of https://shibboleth.atlassian.net/browse/IDP-1020 ?JJDBC-19Resolved issue: JJDBC-19
- Java 17 Stack WorkJJDBC-18Resolved issue: JJDBC-18Rod Widdowson
- ERROR when JSON Parsing with MS SQL ServerJJDBC-17Resolved issue: JJDBC-17Rod Widdowson
- Release Version 1.0.4JJDBC-16Resolved issue: JJDBC-16Rod Widdowson
4 of 4
Re-introduction of https://shibboleth.atlassian.net/browse/IDP-1020 ?
Fixed
Basics
Technical
Logistics
Basics
Technical
Logistics
Description
Environment
Tested with Debian 12 Bookworm, OpenJDK 17, Tomcat 10 and IdP 4.3.1, seems also apply to Debian 11 Bullseye, OpenJDK 11, Tomcat 9 and IdP 4.3.1
Created June 9, 2023 at 8:04 AM
Updated December 3, 2023 at 11:27 AM
Resolved August 11, 2023 at 1:45 PM
Activity
Rod Widdowson December 3, 2023 at 11:27 AM
Rod Widdowson
December 3, 2023 at 11:27 AM
The code has been shipped in V2. No further feedback -> closed
Rod Widdowson August 7, 2023 at 1:23 PM
Rod Widdowson
August 7, 2023 at 1:23 PM
I’ll make that changes as part of this case. Before wednesday
Scott Cantor August 7, 2023 at 12:42 PM
Scott Cantor
August 7, 2023 at 12:42 PM
I think I would leave it, seeing as it really hasn’t come up until now. We do need to apply this same fix to the JDBCPairwiseIdStore in shib-attribute-impl though.
I think that’s about the only other case.
Rod Widdowson August 5, 2023 at 10:43 AM
Rod Widdowson
August 5, 2023 at 10:43 AM
Change made and documented. Leaving open pending question of default
Rod Widdowson August 5, 2023 at 10:29 AM
Rod Widdowson
August 5, 2023 at 10:29 AM
Do we want to flip the Transactional level in this release (the think passed to setTransactionIsolation to “Don’t set”?
We have a monitoring script that authenticates itself via an test sp against our IdP every minute . After successful authentication the monitoring request a SLO. This works a few times, then fails with the following errors:
idp-process.log
postgres db server:
Other users despite the monitoring user may still authentifcate against the IdP but it is rather unresponsive.
This seems the exact behavior reported in .
Reverting to JPA StorageService immediately resolves the issue.
Thank you.