[JIRA] (JJDBC-5) Unable to install JDBC Plugin in idp4.1.0 or 4.2.1
Vivien Wu (Jira)
jira at shibboleth.atlassian.net
Fri Jun 24 17:49:55 UTC 2022
Vivien Wu ( https://shibboleth.atlassian.net/secure/ViewProfile.jspa?accountId=5f0e4b291a26ad001434d48d ) *commented* on JJDBC-5 ( https://shibboleth.atlassian.net/browse/JJDBC-5?atlOrigin=eyJpIjoiOTE3YTI3NDBmYWU2NDJlYzgzOTY3Yjg3NDk1N2I3MzkiLCJwIjoiaiJ9 )
Re: Unable to install JDBC Plugin in idp4.1.0 or 4.2.1 ( https://shibboleth.atlassian.net/browse/JJDBC-5?atlOrigin=eyJpIjoiOTE3YTI3NDBmYWU2NDJlYzgzOTY3Yjg3NDk1N2I3MzkiLCJwIjoiaiJ9 )
Sounds good.. yes, after dropping the two columns, idp has started.
Then.. it ran into something else,
022-06-24 17:33:36,993 - [9AE2077CAD7718A52D1F506403BD42F7] - DEBUG [PROTOCOL_MESSAGE:124] -
<?xml version="1.0" encoding="UTF-8"?><samlp:AuthnRequest xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" AssertionConsumerServiceURL="https://shibsp-dev.iam.stanford.edu/idp-dev/Shibboleth.sso/SAML2/POST" Destination="https://login-dev.stanford.edu/idp/profile/SAML2/Redirect/SSO" ID="_0b524ab4ca7d52023538074e52567f96" IssueInstant="2022-06-24T17:33:36Z" ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Version="2.0">
<saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">https://shibsp-dev.iam.stanford.edu/</saml:Issuer>
<samlp:NameIDPolicy AllowCreate="1"/>
</samlp:AuthnRequest>
2022-06-24 17:33:36,993 - [9AE2077CAD7718A52D1F506403BD42F7] - DEBUG [org.opensaml.profile.action.impl.DecodeMessage:68] - Profile Action DecodeMessage: Incoming request decoded into a message of type org.opensaml.saml.saml2.core.impl.AuthnRequestImpl
2022-06-24 17:33:37,075 - [9AE2077CAD7718A52D1F506403BD42F7] - DEBUG [org.opensaml.profile.action.impl.PopulateClientTLSValidationParameters:143] - Profile Action PopulateClientTLSValidationParameters: Resolving ClientTLSValidationParameters for request
2022-06-24 17:33:37,076 - [9AE2077CAD7718A52D1F506403BD42F7] - DEBUG [org.opensaml.profile.action.impl.PopulateClientTLSValidationParameters:164] - Profile Action PopulateClientTLSValidationParameters: Resolved ClientTLSValidationParameters
2022-06-24 17:33:37,258 - [9AE2077CAD7718A52D1F506403BD42F7] - DEBUG [org.opensaml.profile.action.impl.PopulateDecryptionParameters:139] - Profile Action PopulateDecryptionParameters: Resolving DecryptionParameters for request
2022-06-24 17:33:37,274 - [9AE2077CAD7718A52D1F506403BD42F7] - DEBUG [org.opensaml.profile.action.impl.PopulateDecryptionParameters:161] - Profile Action PopulateDecryptionParameters: Resolved DecryptionParameters
2022-06-24 17:33:37,855 - [9AE2077CAD7718A52D1F506403BD42F7] - DEBUG [net.shibboleth.idp.authn.impl.PopulateAuthenticationContext:213] - Profile Action PopulateAuthenticationContext: Installed 1 potential authentication flows into AuthenticationContext
2022-06-24 17:33:37,864 - [9AE2077CAD7718A52D1F506403BD42F7] - INFO [org.mariadb.jdbc.internal.logging.ProtocolLoggingProxy:128] - conn=377051(M) - 1.065 ms - Query: SELECT version, expires, value FROM StorageRecords WHERE context =? AND id=?, parameters ['b50408140acec74eb625964a0b4216d42a353f2c17a1e052e469b17be08acffd','_session']
2022-06-24 17:33:37,885 - [9AE2077CAD7718A52D1F506403BD42F7] - ERROR [net.shibboleth.idp.authn:-2] - Uncaught runtime exception
net.shibboleth.utilities.java.support.logic.ConstraintViolationException: update: value must not be null
at net.shibboleth.utilities.java.support.logic.Constraint.isNotNull(Constraint.java:307)
2022-06-24 17:33:37,891 - [9AE2077CAD7718A52D1F506403BD42F7] - WARN [org.opensaml.profile.action.impl.LogEvent:101] - A non-proceed event occurred while processing the request: RuntimeException
.. getting error with X509 authn but seems okay with username/password.
I’ll run more tests later.
( https://shibboleth.atlassian.net/browse/JJDBC-5#add-comment?atlOrigin=eyJpIjoiOTE3YTI3NDBmYWU2NDJlYzgzOTY3Yjg3NDk1N2I3MzkiLCJwIjoiaiJ9 ) Add Comment ( https://shibboleth.atlassian.net/browse/JJDBC-5#add-comment?atlOrigin=eyJpIjoiOTE3YTI3NDBmYWU2NDJlYzgzOTY3Yjg3NDk1N2I3MzkiLCJwIjoiaiJ9 )
Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100201- sha1:00501c8 )
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/commits/attachments/20220624/cf2a7700/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-comment-icon-ab3ade46-9768-4e2e-9f3d-ed26578d1d67
Type: image/png
Size: 1084 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220624/cf2a7700/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-avatar-dc94b4d8-24a9-4d73-9f0e-f80f8ddeb67f
Type: image/png
Size: 425 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220624/cf2a7700/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jira-generated-image-static-footer-desktop-logo-73209baf-0d59-47ab-94c6-05122e8da624
Type: image/png
Size: 10805 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/commits/attachments/20220624/cf2a7700/attachment-0005.png>
More information about the commits
mailing list