[JBoss JIRA] (ELY-887) AuthenticationContext IPv6 Address Handling
by Darran Lofthouse (JIRA)
Darran Lofthouse created ELY-887:
------------------------------------
Summary: AuthenticationContext IPv6 Address Handling
Key: ELY-887
URL: https://issues.jboss.org/browse/ELY-887
Project: WildFly Elytron
Issue Type: Task
Components: Authentication Client
Reporter: Darran Lofthouse
Priority: Blocker
Fix For: 1.1.0.Beta20
Within authentication client we need to ensure we are handling IPv6 addresses correctly.
Especially considering an equivalent IPv6 address can have more than one String representation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-7900) Functionality in WildFly to encrypt database passwords
by Carlton Zachary (JIRA)
[ https://issues.jboss.org/browse/WFLY-7900?page=com.atlassian.jira.plugin.... ]
Carlton Zachary commented on WFLY-7900:
---------------------------------------
Hi Darran,
Thanks for your reply. I know of the JBoss vault, but was looking for a more streamlined way of doing this, whether it is encrypted via the CLI or Web console. When using the vault, with several servers in a domain cluster, it becomes time consuming to have to touch each instance in the cluster to add the password to the vault and then add the expression in the password field for each datasource as opposed to doing this all via the CLI or console in a domain.
Thanks again. Looking forward to Elytron.
> Functionality in WildFly to encrypt database passwords
> ------------------------------------------------------
>
> Key: WFLY-7900
> URL: https://issues.jboss.org/browse/WFLY-7900
> Project: WildFly
> Issue Type: Feature Request
> Components: Security
> Affects Versions: 10.1.0.Final
> Reporter: Carlton Zachary
> Assignee: Darran Lofthouse
>
> Is it possible to add functionality to WildFly to encrypt a data source password when the data source is being created? Currently WildFly/EAP stores the password as plain text in the domain.xml/standalone.xml.
> Thanks
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-6626) Add log message indicating disabled <distributable/> flag from web-fragments
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-6626?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-6626:
-----------------------------------------------
Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1337858|https://bugzilla.redhat.com/show_bug.cgi?id=1337858] from VERIFIED to CLOSED
> Add log message indicating disabled <distributable/> flag from web-fragments
> ----------------------------------------------------------------------------
>
> Key: WFLY-6626
> URL: https://issues.jboss.org/browse/WFLY-6626
> Project: WildFly
> Issue Type: Enhancement
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Final
> Reporter: Aaron Ogburn
> Assignee: Stuart Douglas
> Fix For: 10.1.0.CR1, 10.1.0.Final
>
> Attachments: undistributable.war
>
>
> If a web-fragment doesn't have distributable set, then replication is not enabled. This happens silently so it may be confusing to some users that are expecting replication to be enabled when they have set <distributable/> in their WEB-INF/web.xml.
> Other third party libraries they included may have web-fragments without distributable set so it'd be nice to log a notification when this happens so that users are easily informed why replication was not enabled as they may have expected.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-6402) EJBs accessible too early (spec violation)
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-6402?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-6402:
-----------------------------------------------
Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1350355|https://bugzilla.redhat.com/show_bug.cgi?id=1350355] from VERIFIED to CLOSED
> EJBs accessible too early (spec violation)
> ------------------------------------------
>
> Key: WFLY-6402
> URL: https://issues.jboss.org/browse/WFLY-6402
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Fedor Gavrilov
> Labels: downstream_dependency
> Attachments: auto-test-reproducer.zip
>
>
> {code}
> EJB 3.1 spec, section 4.8.1:
> "If the Startup annotation appears on the Singleton bean class or if the Singleton has been designated via the deployment descriptor as requiring eager initialization, the container must initialize the Singleton bean instance during the application startup sequence. The container must initialize all such startup-time Singletons before any external client requests (that is, client requests originating outside of the application) are delivered to any enterprise bean components in the application.
> {code}
> Wildlfy does not implement this correctly, and allows calls to other EJBs before a @Startup @Singleton finishes its @PostConstruct call.
> This Jira ticket handles two PR's on WFLY:
> https://github.com/wildfly/wildfly/pull/8824 (that is already merged)
> and https://github.com/wildfly/wildfly/pull/8989
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFLY-5995) Initial calculation of the first expiration time for a scheduled timer is wrong if a start date is set
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-5995?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-5995:
-----------------------------------------------
Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1298651|https://bugzilla.redhat.com/show_bug.cgi?id=1298651] from VERIFIED to CLOSED
> Initial calculation of the first expiration time for a scheduled timer is wrong if a start date is set
> ------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5995
> URL: https://issues.jboss.org/browse/WFLY-5995
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 8.2.1.Final, 9.0.2.Final, 10.0.0.CR5
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Labels: timers, timerservice
> Fix For: 10.0.0.Final
>
>
> If a scheduled timer should be created with the following parameters:
> ScheduleExpression[second=0 minute=0/5 hour=20-22 dayOfWeek=* dayOfMonth=* month=* year=* start=Thu Jan 14 09:45:35 GMT+1 2016]
> The first schedule should be
> Thu Jan 17 20:00:20 GMT+1 2016
> but is calculated as
> Sun Jan 17 20:45:35 GMT+1 2016
> The minutes are not correctly set according to the schedule and the given start date.
> This happen for seconds/minutes if the ScheduleExpression limit the range.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFCORE-2203) Outcome from /host=x/server-config=y:remove() operation in managed domain with multiple hosts lists out all the steps in result
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2203?page=com.atlassian.jira.plugi... ]
Brian Stansberry reassigned WFCORE-2203:
----------------------------------------
Assignee: ehsavoie Hugonnet (was: Brian Stansberry)
> Outcome from /host=x/server-config=y:remove() operation in managed domain with multiple hosts lists out all the steps in result
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2203
> URL: https://issues.jboss.org/browse/WFCORE-2203
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Michal Jurc
> Assignee: ehsavoie Hugonnet
>
> Outcome of successful removal of a server controlled by a slave HC in managed domain with multiple hosts lists outcomes of all the steps, polluting the CLI:
> {code} [domain@localhost:9990 /] /host=msimka-t450.brq.redhat.com/server-config=server-one:remove
> {
> "outcome" => "success",
> "result" => {
> "step-1" => {"outcome" => "success"},
> "step-2" => {"outcome" => "success"},
> "step-3" => {"outcome" => "success"},
> "step-4" => {"outcome" => "success"},
> "step-5" => {"outcome" => "success"},
> "step-6" => {"outcome" => "success"},
> "step-7" => {"outcome" => "success"},
> "step-8" => {"outcome" => "success"},
> "step-9" => {"outcome" => "success"},
> "step-10" => {"outcome" => "success"},
> "step-11" => {"outcome" => "success"},
> "step-12" => {"outcome" => "success"},
> "step-13" => {"outcome" => "success"},
> "step-14" => {"outcome" => "success"},
> "step-15" => {"outcome" => "success"},
> "step-16" => {"outcome" => "success"},
> "step-17" => {"outcome" => "success"},
> "step-18" => {"outcome" => "success"},
> "step-19" => {"outcome" => "success"},
> "step-20" => {"outcome" => "success"},
> "step-21" => {"outcome" => "success"},
> "step-22" => {"outcome" => "success"},
> "step-23" => {"outcome" => "success"},
> "step-24" => {"outcome" => "success"},
> "step-25" => {"outcome" => "success"},
> "step-26" => {"outcome" => "success"},
> "step-27" => {"outcome" => "success"},
> "step-28" => {"outcome" => "success"},
> "step-29" => {"outcome" => "success"},
> "step-30" => {"outcome" => "success"},
> "step-31" => {"outcome" => "success"},
> "step-32" => {"outcome" => "success"},
> "step-33" => {"outcome" => "success"},
> "step-34" => {"outcome" => "success"},
> "step-35" => {"outcome" => "success"},
> "step-36" => {
> "outcome" => "success",
> "result" => undefined
> },
> "step-37" => {"outcome" => "success"},
> "step-38" => {"outcome" => "success"},
> "step-39" => {"outcome" => "success"},
> "step-40" => {"outcome" => "success"},
> "step-41" => {"outcome" => "success"},
> "step-42" => {"outcome" => "success"},
> "step-43" => {"outcome" => "success"},
> "step-44" => {"outcome" => "success"},
> "step-45" => {"outcome" => "success"},
> "step-46" => {"outcome" => "success"},
> "step-47" => {"outcome" => "success"},
> "step-48" => {"outcome" => "success"},
> "step-49" => {"outcome" => "success"},
> "step-50" => {"outcome" => "success"},
> "step-51" => {"outcome" => "success"},
> "step-52" => {"outcome" => "success"},
> "step-53" => {"outcome" => "success"},
> "step-54" => {"outcome" => "success"},
> "step-55" => {"outcome" => "success"},
> "step-56" => {"outcome" => "success"},
> "step-57" => {"outcome" => "success"},
> "step-58" => {"outcome" => "success"},
> "step-59" => {"outcome" => "success"},
> "step-60" => {"outcome" => "success"},
> "step-61" => {"outcome" => "success"},
> "step-62" => {"outcome" => "success"},
> "step-63" => {"outcome" => "success"},
> "step-64" => {"outcome" => "success"},
> "step-65" => {"outcome" => "success"},
> "step-66" => {"outcome" => "success"},
> "step-67" => {"outcome" => "success"},
> "step-68" => {"outcome" => "success"},
> "step-69" => {"outcome" => "success"},
> "step-70" => {"outcome" => "success"},
> "step-71" => {"outcome" => "success"},
> "step-72" => {"outcome" => "success"},
> "step-73" => {"outcome" => "success"},
> "step-74" => {"outcome" => "success"},
> "step-75" => {"outcome" => "success"},
> "step-76" => {"outcome" => "success"},
> "step-77" => {"outcome" => "success"},
> "step-78" => {"outcome" => "success"},
> "step-79" => {"outcome" => "success"},
> "step-80" => {"outcome" => "success"},
> "step-81" => {"outcome" => "success"},
> "step-82" => {"outcome" => "success"},
> "step-83" => {"outcome" => "success"},
> "step-84" => {"outcome" => "success"},
> "step-85" => {"outcome" => "success"},
> "step-86" => {"outcome" => "success"},
> "step-87" => {"outcome" => "success"},
> "step-88" => {"outcome" => "success"},
> "step-89" => {"outcome" => "success"},
> "step-90" => {"outcome" => "success"},
> "step-91" => {"outcome" => "success"},
> "step-92" => {"outcome" => "success"},
> "step-93" => {"outcome" => "success"},
> "step-94" => {"outcome" => "success"},
> "step-95" => {"outcome" => "success"},
> "step-96" => {"outcome" => "success"},
> "step-97" => {"outcome" => "success"},
> "step-98" => {"outcome" => "success"},
> "step-99" => {"outcome" => "success"},
> "step-100" => {"outcome" => "success"},
> "step-101" => {"outcome" => "success"},
> "step-102" => {"outcome" => "success"},
> "step-103" => {"outcome" => "success"},
> "step-104" => {"outcome" => "success"},
> "step-105" => {"outcome" => "success"},
> "step-106" => {"outcome" => "success"},
> "step-107" => {"outcome" => "success"},
> "step-108" => {"outcome" => "success"},
> "step-109" => {"outcome" => "success"},
> "step-110" => {"outcome" => "success"},
> "step-111" => {"outcome" => "success"},
> "step-112" => {"outcome" => "success"},
> "step-113" => {"outcome" => "success"},
> "step-114" => {"outcome" => "success"},
> "step-115" => {"outcome" => "success"},
> "step-116" => {"outcome" => "success"},
> "step-117" => {"outcome" => "success"},
> "step-118" => {"outcome" => "success"},
> "step-119" => {"outcome" => "success"},
> "step-120" => {"outcome" => "success"},
> "step-121" => {"outcome" => "success"},
> "step-122" => {"outcome" => "success"},
> "step-123" => {"outcome" => "success"},
> "step-124" => {"outcome" => "success"},
> "step-125" => {"outcome" => "success"},
> "step-126" => {"outcome" => "success"},
> "step-127" => {"outcome" => "success"},
> "step-128" => {"outcome" => "success"},
> "step-129" => {"outcome" => "success"},
> "step-130" => {"outcome" => "success"},
> "step-131" => {"outcome" => "success"},
> "step-132" => {"outcome" => "success"},
> "step-133" => {"outcome" => "success"},
> "step-134" => {"outcome" => "success"},
> "step-135" => {"outcome" => "success"},
> "step-136" => {"outcome" => "success"},
> "step-137" => {"outcome" => "success"},
> "step-138" => {"outcome" => "success"},
> "step-139" => {"outcome" => "success"},
> "step-140" => {"outcome" => "success"},
> "step-141" => {"outcome" => "success"},
> "step-142" => {"outcome" => "success"},
> "step-143" => {"outcome" => "success"},
> "step-144" => {"outcome" => "success"},
> "step-145" => {"outcome" => "success"},
> "step-146" => {"outcome" => "success"},
> "step-147" => {"outcome" => "success"},
> "step-148" => {"outcome" => "success"},
> "step-149" => {"outcome" => "success"},
> "step-150" => {"outcome" => "success"},
> "step-151" => {"outcome" => "success"},
> "step-152" => {"outcome" => "success"},
> "step-153" => {"outcome" => "success"},
> "step-154" => {"outcome" => "success"},
> "step-155" => {"outcome" => "success"},
> "step-156" => {"outcome" => "success"},
> "step-157" => {"outcome" => "success"},
> "step-158" => {"outcome" => "success"},
> "step-159" => {"outcome" => "success"},
> "step-160" => {"outcome" => "success"},
> "step-161" => {"outcome" => "success"},
> "step-162" => {"outcome" => "success"},
> "step-163" => {"outcome" => "success"},
> "step-164" => {"outcome" => "success"},
> "step-165" => {"outcome" => "success"},
> "step-166" => {"outcome" => "success"},
> "step-167" => {"outcome" => "success"},
> "step-168" => {"outcome" => "success"},
> "step-169" => {"outcome" => "success"},
> "step-170" => {"outcome" => "success"},
> "step-171" => {"outcome" => "success"},
> "step-172" => {"outcome" => "success"},
> "step-173" => {"outcome" => "success"},
> "step-174" => {"outcome" => "success"},
> "step-175" => {"outcome" => "success"},
> "step-176" => {"outcome" => "success"},
> "step-177" => {"outcome" => "success"},
> "step-178" => {"outcome" => "success"},
> "step-179" => {"outcome" => "success"},
> "step-180" => {"outcome" => "success"},
> "step-181" => {"outcome" => "success"},
> "step-182" => {"outcome" => "success"},
> "step-183" => {"outcome" => "success"},
> "step-184" => {"outcome" => "success"},
> "step-185" => {"outcome" => "success"},
> "step-186" => {"outcome" => "success"},
> "step-187" => {"outcome" => "success"},
> "step-188" => {"outcome" => "success"},
> "step-189" => {"outcome" => "success"},
> "step-190" => {"outcome" => "success"},
> "step-191" => {"outcome" => "success"},
> "step-192" => {"outcome" => "success"},
> "step-193" => {"outcome" => "success"},
> "step-194" => {"outcome" => "success"},
> "step-195" => {"outcome" => "success"},
> "step-196" => {"outcome" => "success"},
> "step-197" => {"outcome" => "success"},
> "step-198" => {"outcome" => "success"},
> "step-199" => {"outcome" => "success"},
> "step-200" => {"outcome" => "success"},
> "step-201" => {"outcome" => "success"},
> "step-202" => {"outcome" => "success"},
> "step-203" => {"outcome" => "success"},
> "step-204" => {"outcome" => "success"},
> "step-205" => {"outcome" => "success"},
> "step-206" => {"outcome" => "success"},
> "step-207" => {"outcome" => "success"},
> "step-208" => {"outcome" => "success"},
> "step-209" => {"outcome" => "success"},
> "step-210" => {"outcome" => "success"},
> "step-211" => {"outcome" => "success"},
> "step-212" => {"outcome" => "success"},
> "step-213" => {"outcome" => "success"},
> "step-214" => {"outcome" => "success"},
> "step-215" => {"outcome" => "success"},
> "step-216" => {"outcome" => "success"},
> "step-217" => {"outcome" => "success"},
> "step-218" => {"outcome" => "success"},
> "step-219" => {"outcome" => "success"},
> "step-220" => {"outcome" => "success"},
> "step-221" => {"outcome" => "success"},
> "step-222" => {"outcome" => "success"},
> "step-223" => {"outcome" => "success"},
> "step-224" => {"outcome" => "success"},
> "step-225" => {"outcome" => "success"},
> "step-226" => {"outcome" => "success"},
> "step-227" => {"outcome" => "success"},
> "step-228" => {"outcome" => "success"},
> "step-229" => {"outcome" => "success"},
> "step-230" => {"outcome" => "success"},
> "step-231" => {"outcome" => "success"},
> "step-232" => {"outcome" => "success"},
> "step-233" => {"outcome" => "success"},
> "step-234" => {"outcome" => "success"},
> "step-235" => {"outcome" => "success"},
> "step-236" => {"outcome" => "success"},
> "step-237" => {"outcome" => "success"}
> },
> "server-groups" => undefined
> }
> {code}
> If the server is controlled by the master the response is normal. If the CLI connects directly to the slave (i.e. not routing through the master) the output is as shown above.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months