-
Bug
-
Resolution: Done
-
Blocker
-
7.1.0.DR10
-
-
-
-
-
-
Not Required
-
When http management interface is secured with kerberos in legacy security solution.
- By accessing management interface with browser (e.g. http://localhost.localdomain:9990/management?operation=attribute&name=server-state ) http status code 403 is returned instead of 401. That mean also there is no http header "WWW-Authenticate: Negotiate". So authentication with kerberos ticket is not even tried.
- By accessing http management intarface with jboss-cli output is
1: Failed to connect to the controller: Unable to authenticate against controller at localhost.localdomain:9990: Authentication failed: the server presented no authentication mechanisms
This is regression against EAP 7.0. Customers migrating to EAP 7.1 won't be able to continue using this feature.
- is incorporated by
-
JBEAP-7960 (7.1.0) Upgrade to WildFly Core to 3.0.0.Alpha22
- Closed
- is related to
-
WFCORE-1955 Wrap Kerberos behaviour of legacy realms with Elytron components
- Resolved
- relates to
-
JBEAP-13129 Fix/unignore KerberosServerIdentityTestCase
- Pull Request Sent