[jboss-jira] [JBoss JIRA] (WFLY-6614) add trace logging to the SSO code in wildfly/undertow
Ingo Weiss (JIRA)
issues at jboss.org
Mon May 16 11:02:01 EDT 2016
[ https://issues.jboss.org/browse/WFLY-6614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ingo Weiss moved JBEAP-4595 to WFLY-6614:
-----------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-6614 (was: JBEAP-4595)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
Web (Undertow)
(was: Web (Undertow))
Target Release: (was: 7.0.z.GA)
Fix Version/s: (was: 7.0.1.GA)
Release Notes Docs Status: (was: Documented as Known Issue)
> add trace logging to the SSO code in wildfly/undertow
> -----------------------------------------------------
>
> Key: WFLY-6614
> URL: https://issues.jboss.org/browse/WFLY-6614
> Project: WildFly
> Issue Type: Bug
> Components: Security, Web (Undertow)
> Reporter: Ingo Weiss
> Assignee: Ingo Weiss
> Priority: Critical
>
> Please add trace logging to the SSO code in wildfly/undertow.
> For example, it would be helpful if the sso code logged that it was getting triggered, if re-authentication was happening, etc.
> This is going to be very difficult to support if we do not have this type of information.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list