Help tracking down an uncaught exception

Duncan Brannen dbb at st-andrews.ac.uk
Mon Oct 24 09:47:54 UTC 2022


 

Morning,

                I've a remote user signing in to our IDP (SAML2 HTTP Post)
using a VirtualBox Ubuntu VM who gets a 500 error before any kind of
authentication prompt. (Client is Cisco Anyconnect which works fine outside
of Virtualbox from our testing )

 

I've got the log level at Debug, and aside from timestamps/JsessionIDs,
there's no difference between the logs for his connection vs my successful
connection until the uncaught exception error.

 

This is a snippet of the logs for the unsuccessful request 

 

2022-10-04 14:22:10,514 - [117477BDB2537A3F521C6B9423BDEABD] -
aaa.bbb.126.12 - DEBUG
[net.shibboleth.idp.authn.impl.PopulateAuthenticationContext:213] - Profile
Action PopulateAuthenticationContext: Installed 1 potential authentication
flows into AuthenticationContext

2022-10-04 14:22:10,514 - [117477BDB2537A3F521C6B9423BDEABD] -
aaa.bbb.126.12 - DEBUG
[net.shibboleth.idp.session.impl.PopulateSessionContext:145] - Profile
Action PopulateSessionContext: No session found for client

2022-10-04 14:22:10,533 - [117477BDB2537A3F521C6B9423BDEABD] -
aaa.bbb.126.12 - ERROR [net.shibboleth.idp.authn:-2] - Uncaught runtime
exception

2022-10-04 14:22:10,535 - [117477BDB2537A3F521C6B9423BDEABD] -
aaa.bbb.126.12 - WARN [org.opensaml.profile.action.impl.LogEvent:101] - A
non-proceed event occurred while processing the request: RuntimeException

 

Vs the successful one

 

2022-10-04 12:03:33,630 - [0D861F4157D7245C22D2DC14AE1BB047] -
ccc.ddd.228.248 - DEBUG
[net.shibboleth.idp.authn.impl.PopulateAuthenticationContext:213] - Profile
Action PopulateAuthenticationContext: Installed 1 potential authentication
flows into AuthenticationContext

2022-10-04 12:03:33,630 - [0D861F4157D7245C22D2DC14AE1BB047] -
ccc.ddd.228.248 - DEBUG
[net.shibboleth.idp.session.impl.PopulateSessionContext:145] - Profile
Action PopulateSessionContext: No session found for client

2022-10-04 12:03:33,631 - [0D861F4157D7245C22D2DC14AE1BB047] -
ccc.ddd.228.248 - DEBUG
[net.shibboleth.idp.authn.impl.InitializeRequestedPrincipalContext:152] -
Profile Action InitializeRequestedPrincipalContext: Profile configuration
did not supply any default authentication methods

2022-10-04 12:03:33,631 - [0D861F4157D7245C22D2DC14AE1BB047] -
ccc.ddd.228.248 - DEBUG
[net.shibboleth.idp.authn.impl.FilterFlowsByForcedAuthn:76] - Profile Action
FilterFlowsByForcedAuthn: Retaining flow authn/SAML, it supports forced
authentication

2022-10-04 12:03:33,631 - [0D861F4157D7245C22D2DC14AE1BB047] -
ccc.ddd.228.248 - DEBUG
[net.shibboleth.idp.authn.impl.FilterFlowsByForcedAuthn:88] - Profile Action
FilterFlowsByForcedAuthn: Potential authentication flows left after
filtering: [authn/SAML]

 

 

Any thoughts on where I can go from here to try and find the reason for the
client being returned a 500 error?

 

Thanks,

                Duncan 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20221024/3b056b3c/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6748 bytes
Desc: not available
URL: <http://shibboleth.net/pipermail/users/attachments/20221024/3b056b3c/attachment.p7s>


More information about the users mailing list