Listener not dispatching getHeaders message

[Benjamin Ryan]

Scott,
	I have modified the logging to use the tranLogFormat the results are as follows:

	Shibd.log:

		2013-07-11 13:42:56 DEBUG Shibboleth.SSO.SAML2 [2]: ACS returning via redirect to: https://content.resourceshare.ac.uk//xmlui/shibboleth-login
	2013-07-11 13:42:56 DEBUG Shibboleth.Listener [2]: dispatching message (find::StorageService::SessionCache)
	2013-07-11 13:42:56 DEBUG XMLTooling.StorageService [2]: updated expiration of valid records in context (_c13cf629e45554925b8840f42be7632b) to (1373551076)
	2013-07-11 13:42:56 DEBUG Shibboleth.Listener [2]: dispatching message (remove::StorageService::SessionCache)
	2013-07-11 13:42:56 INFO Shibboleth.SessionCache [2]: removed session (_c13cf629e45554925b8840f42be7632b)

	Transaction.log:

		2013-07-11 13:33:02 INFO Shibboleth-TRANSACTION.AuthnRequest [1]:      default   
		2013-07-11 13:33:11 INFO Shibboleth-TRANSACTION.Login [2]:   urn:oasis:names:tc:SAML:2.0:status:Success   default 8a8b8db3ccf5caee7d564f95f7492217872ea72521d97eb8bf3a791f98fc5102 urn:oasis:nam
es:tc:SAML:2.0:ac:classes:PasswordProtectedTransport affiliation(2),net-id(1)

	No information about the session termination is listed in the transaction log.

Regards,
	Ben
------------------------------------------------------------------
Dr Ben Ryan
Jorum Technical Manager

5.12 Roscoe Building
The University of Manchester
Oxford Road
Manchester
M13 9PL
Tel: 0160 275 6039
E-mail: benjamin.ryan at manchester.ac.uk
------------------------------------------------------------------


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: 10 July 2013 14:58
To: Shib Users
Subject: Re: Listener not dispatching getHeaders message

On 7/10/13 9:55 AM, "Benjamin Ryan" <benjamin.ryan at manchester.ac.uk> wrote:

>               The only difference I can see in the logs is that the 
>working system dispatches the default::getHeaders::Application message 
>and the non-working system does not, it just proceeds to remove the 
>newly created session.
>               Can anyone help with where I should look at next?

native.log

The removal of the session means it's being flagged as invalid, so there should be something about why, unless I didn't get the logging fixed as I intended. The other difference isn't relevant, just an internal detail.

-- Scott


--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net