[jboss-jira] [JBoss JIRA] (WFCORE-2641) Authentication through http-interface with Elytron authentication and legacy SSL (without configured authentication) is not possible

[ehsavoie Hugonnet (JIRA)]

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

ehsavoie Hugonnet resolved WFCORE-2641.
---------------------------------------
    Fix Version/s: 3.0.0.Beta26
         Assignee: Darran Lofthouse
       Resolution: Done


Resolved as JBEAP cloned from is verified

> Authentication through http-interface with Elytron authentication and legacy SSL (without configured authentication) is not possible
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-2641
>                 URL: https://issues.jboss.org/browse/WFCORE-2641
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Domain Management, Security
>    Affects Versions: 3.0.0.Beta13
>            Reporter: Ondrej Lukas
>            Assignee: Darran Lofthouse
>            Priority: Blocker
>             Fix For: 3.0.0.Beta26
>
>
> When http-interface uses http-authentication-factory attribute for authentication and security-realm attribute for SSL, and referenced security-realm does not include authentication, then authentication through http-interface is not possible.
> When Management Console is used, then page with _The Red Hat JBoss Enterprise Application Platform 7 is running. However you have not yet added any users to be able to access the admin console._ is displayed.
> When https://localhost:9993/management?operation=attribute&name=server-state is accessed then following output is returned:
> {code}
> {
>     "outcome" : "failed",
>     "failure-description" : "WFLYDMHTTP0006: The security realm is not ready to process requests, see https://localhost:9993/error",
>     "rolled-back" : "true"
> }
> {code}
> When security-realm includes also authentication (which is not used) then authentication through http-interface works as expected.



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