Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Error handling should have access to the message type.

Description

I don't think the error templates or redirection option have any visibility into what the actual message is/was if a SAML status failure is raised. That causes a serious problem when you can't distinguish between a SSO or logout failure, and with the IdP starting to support logout, sort of, logout failure will be a very, very common outcome.

Environment

None

Activity

Show:

Scott Cantor June 2, 2016 at 6:06 PM

ff989541a39dedc754eddd2b581ebe1a146d6afa

Catch additional path where handler gets run.

Scott Cantor June 2, 2016 at 6:02 PM

cca2ce814d7aee7b9bf90a7c68dbd8d85baef709

Added an eventType property and added it to any exceptions raised during handler execution via a property added to the Handler interface. Reused the TransactionLog Event types for it.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Fix versions

Created April 13, 2016 at 3:49 PM
Updated June 29, 2016 at 4:22 PM
Resolved June 2, 2016 at 6:02 PM

Flag notifications