> Does anybody have an idea of why this is happening? It's expected behavior. A service ticket is created (INSERT) and subsequently validated (DELETE) in a short time interval under normal circumstances, so it's likely you're simply examining the database after it has already been deleted. If you want to confirm storage, you'll need to intercept the ticket (using a Web proxy, for example) prior to validation, query the DB to confirm it's there, then allow the service to validate it. Note this will likely cause validation to fail since you have on 10s by default, so the ticket will likely be expired by the time it's validated if you are using manual processes to intercept the ticket and query for it.
M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
