Bug 1490383 - Auth plugin stopped working on Wildfly 11
Summary: Auth plugin stopped working on Wildfly 11
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.2.0
: 4.2.0
Assignee: Roy Golan
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-11 12:48 UTC by Roy Golan
Modified: 2018-02-12 10:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Wildfly auth plugins code is initiating the ovirt plugin with a null parameter Consequence: ovirt auth plugins fails to load - login into the wildfly management console fails constantly. Fix: ignore the passed parameter, it is not needed for ovirt auth plugin anyway. Result: ovirt auth plugin is loaded and access to the management console with proper admin credentials is working.
Clone Of:
Environment:
Last Closed: 2018-02-12 10:12:14 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-9338 0 Major Resolved sharedState is passed null by PluginAuthenticationCallbackHandler 2018-01-30 13:36:30 UTC
oVirt gerrit 81614 0 master POST core: Check nullness on init of auth-plugin 2017-09-11 12:49:49 UTC

Description Roy Golan 2017-09-11 12:48:13 UTC
Description of problem:
The move to Wildfly 11 is resulting an NPE when initiating the AuthPlugIn because a sharedState argument passed by the a container callnack is now null. This was working fine on Wildfly 10

Related Wildfly issue https://issues.jboss.org/browse/WFLY-9338


Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. jbosscli or open http://localhost:8706 and try to login

Actual results:
fail to login to mgmt consule

Expected results:
Login to mgmt console

Additional info:

Comment 1 Martin Perina 2017-09-12 07:56:46 UTC
This is only failsafe to not block whole oVirt startup, but this issue needs to be fixed in WildFly

Comment 2 Yaniv Kaul 2017-10-15 13:06:56 UTC
Patch is merged already - anything needed here or can it move to MODIFIED?

Comment 3 Roy Golan 2017-10-15 13:42:11 UTC
to verify run:

    /usr/share/ovirt-engine-wildfly/bin/jboss-cli.sh \
    --controller=remote+http://127.0.0.1:8706 \
    --connect --user=admin@internal 

you should see the prompt:

    [standalone.0.1:8706 /]

Comment 4 Lukas Svaty 2018-01-30 13:36:24 UTC
verified in ovirt-engine-4.2.1.4-0.1.el7.noarch

Comment 5 Sandro Bonazzola 2018-02-12 10:12:14 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.