[jboss-jira] [JBoss JIRA] (WFCORE-2438) Legacy Kerberos for management interface returns 500 instead of 401

[Kabir Khan (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kabir Khan resolved WFCORE-2438.
--------------------------------
    Resolution: Done


[~dlofthouse] The linked JBEAP was incorporated by the core release, so I am assuming this is done as well

> Legacy Kerberos for management interface returns 500 instead of 401
> -------------------------------------------------------------------
>
>                 Key: WFCORE-2438
>                 URL: https://issues.jboss.org/browse/WFCORE-2438
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Security
>            Reporter: Martin Choma
>            Assignee: Darran Lofthouse
>            Priority: Critical
>             Fix For: 3.0.0.Beta12
>
>
> On first access server should response with 401 http code. Subsequent response could be 500, as it express properly server is misconfigured. In EAP 7.0 it was 403, that is not ideal as 403 mean user is authenticated but has not proper roles, which is not true in this case. 
> Also some ERROR log message would be helpful for administrators to find cause of problem. Now there are just TRACE level messages
> {code:title=server.log}
> 07:40:04,134 TRACE [org.jboss.as.domain.management.security] (management task-6) No mapping for name 'http/localhost.localdomain' to KeytabService, attempting to use host only match.
> 07:40:04,135 TRACE [org.jboss.as.domain.management.security] (management task-6) No mapping for host 'localhost.localdomain' to KeytabService, attempting to use default.
> 07:40:04,135 TRACE [org.jboss.as.domain.management.security] (management task-6) No KeytabService available for host 'localhost.localdomain' unable to return SubjectIdentity.
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)