[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ]
Elizabeth Clayton edited comment on DROOLS-4972 at 1/30/20 1:32 PM:
--------------------------------------------------------------------
[~yamer] I took a closer look and imo this needs it's own jira, to support a more comprehensive fix. But in the interim, unless I'm misunderstanding the interaction, it might help to:
- When it's not in "edit mode" consider moving the "Add new item" directly below the last item in the list.
- Consider renaming the action to "Add list value" or whatever most closely describes the action.
- Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, while the "Add new item" looks about right.
!Screen Shot 2020-01-30 at 1.24.18 PM.png|thumbnail!
- Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
Thanks!
Liz
was (Author: uxdlc):
[~yamer] I took a closer look and imo this needs it's own jira, to support a more comprehensive fix. But in the interim, unless I'm misunderstanding the interaction, it might help to:
- Move the "Add new item" directly below the last item in the list.
- Consider renaming the action to "Add list value" or whatever most closely describes the action.
- Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, while the "Add new item" looks about right.
!Screen Shot 2020-01-30 at 1.24.18 PM.png|thumbnail!
- Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
Thanks!
Liz
> Buttons stay disabled when switching to textual collection editor
> -----------------------------------------------------------------
>
> Key: DROOLS-4972
> URL: https://issues.redhat.com/browse/DROOLS-4972
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm
>
>
> If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ]
Elizabeth Clayton updated DROOLS-4972:
--------------------------------------
Attachment: Screen Shot 2020-01-30 at 1.24.18 PM.png
> Buttons stay disabled when switching to textual collection editor
> -----------------------------------------------------------------
>
> Key: DROOLS-4972
> URL: https://issues.redhat.com/browse/DROOLS-4972
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm
>
>
> If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor
by Elizabeth Clayton (Jira)
[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ]
Elizabeth Clayton commented on DROOLS-4972:
-------------------------------------------
[~yamer] I took a closer look and imo this needs it's own jira, to support a more comprehensive fix. But in the interim, unless I'm misunderstanding the interaction, it might help to:
- Move the "Add new item" directly below the last item in the list.
- Consider renaming the action to "Add list value" or whatever most closely describes the action.
- Consider making the font sizes the same within the dialog. The Name field looks too small, while the Edit name looks too large, while the "Add new item" looks about right.
!Screen Shot 2020-01-30 at 1.24.18 PM.png|thumbnail!
- Also when the Edit form is open is it scrolled out of view by default. Maybe as a short term patch could the area auto scroll somehow to make sure the form area is in view? Would be best to just redesign this though in the long run imo.
Thanks!
Liz
> Buttons stay disabled when switching to textual collection editor
> -----------------------------------------------------------------
>
> Key: DROOLS-4972
> URL: https://issues.redhat.com/browse/DROOLS-4972
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Affects Versions: 7.32.0.Final
> Reporter: Jozef Marko
> Assignee: Yeser Amer
> Priority: Minor
> Labels: drools-tools
> Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm
>
>
> If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFCORE-4820) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
by Ilia Vassilev (Jira)
[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ]
Ilia Vassilev updated WFCORE-4820:
----------------------------------
Labels: downstream_dependency (was: )
> Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4820
> URL: https://issues.redhat.com/browse/WFCORE-4820
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security
> Affects Versions: 10.0.3.Final
> Reporter: Mark Sanchez
> Assignee: Darran Lofthouse
> Priority: Major
> Labels: downstream_dependency
> Fix For: 11.0.0.Beta8
>
>
> error:
> WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> We get an error with the following ldap configuration. This works for version 17.
> <security-realm name="ldap_security_realm">
> <server-identities>
> <ssl>
> <engine enabled-protocols="TLSv1.2"/>
> <keystore path="/opt/app/workload/jboss/ssl_jboss/psftest2s.jboss.keystore" keystore-password="${VAULT::ssl_cert::password::1}"/>
> </ssl>
> </server-identities>
> <authentication>
> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
> <username-filter attribute="samaccountname"/>
> </ldap>
> </authentication>
> </security-realm>
> </security-realms>
> <outbound-connections>
> <ldap name="testLdap" url="ldap://its-ad-ldap.it.test.com:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="${VAULT::ldap_searchdn::password::1}" security-realm="ldap_security_realm"/>
> </outbound-connections>
> <management-interfaces>
> <http-interface security-realm="ldap_security_realm">
> <http-upgrade enabled="true"/>
> <socket interface="management" port="${jboss.management.http.port:9990}"/>
> </http-interface>
> </management-interfaces>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFCORE-4828) Errors Missing on Invalid Configuration
by James Perkins (Jira)
James Perkins created WFCORE-4828:
-------------------------------------
Summary: Errors Missing on Invalid Configuration
Key: WFCORE-4828
URL: https://issues.redhat.com/browse/WFCORE-4828
Project: WildFly Core
Issue Type: Bug
Components: Security
Affects Versions: 11.0.0.Beta7
Reporter: Darran Lofthouse
Assignee: Richard Opalka
[~ropalka] I believe this is caused by the MSC refactoring.
Steps, in the default host.xml for domain mode.
1. Define the following security realm: -
{noformat}
<security-realms>
<security-realm name="ldap_security_realm">
<server-identities>
<ssl>
<keystore path="generated.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/>
</ssl>
</server-identities>
<authentication>
<ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
<username-filter attribute="samaccountname"/>
</ldap>
</authentication>
</security-realm>
{noformat}
2. Define the following outbound connection: -
{noformat}
<outbound-connections>
<ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" />
</outbound-connections>
{noformat}
3. Update the management interfaces to: -
{noformat}
<management-interfaces>
<http-interface security-realm="ldap_security_realm">
<http-upgrade enabled="true"/>
<socket interface="management" port="${jboss.management.http.port:9990}"/>
</http-interface>
</management-interfaces>
{noformat}
The server fails to boot with just the following error: -
{noformat}
[Host Controller] 17:56:40,052 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.
{noformat}
If the management interface is then updated to reference the ManagementRealm instead the error is now: -
{noformat}
[Host Controller] 18:01:48,595 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
[Host Controller] ("host" => "master"),
[Host Controller] ("core-service" => "management"),
[Host Controller] ("security-realm" => "ldap_security_realm")
[Host Controller] ]) - failure description: {
[Host Controller] "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"jboss.server.config.dir\""],
[Host Controller] "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.core.management.security.realm.ldap_security_realm.key-manager is missing [jboss.server.path.\"jboss.server.config.dir\"]"]
[Host Controller] }
{noformat}
This error is expected as the realm defined in step 1 referenced an invalid path.
I believe the error reporting should come from this method: -
org.jboss.as.controller.ServiceVerificationHelper.execute(OperationContext, ModelNode)
However something seems to have changes with the MSC migration.
This was recently encountered debugging the bug report in https://issues.redhat.com/browse/WFCORE-4820, if you see an error "Multiple CallbackHandlerServices for the same mechanism (PLAIN)" that has been covered by WFCORE-4820.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFCORE-4827) Errors Missing on Invalid Configuration
by Darran Lofthouse (Jira)
Darran Lofthouse created WFCORE-4827:
----------------------------------------
Summary: Errors Missing on Invalid Configuration
Key: WFCORE-4827
URL: https://issues.redhat.com/browse/WFCORE-4827
Project: WildFly Core
Issue Type: Bug
Components: Security
Affects Versions: 11.0.0.Beta7
Reporter: Darran Lofthouse
Assignee: Richard Opalka
[~ropalka] I believe this is caused by the MSC refactoring.
Steps, in the default host.xml for domain mode.
1. Define the following security realm: -
{noformat}
<security-realms>
<security-realm name="ldap_security_realm">
<server-identities>
<ssl>
<keystore path="generated.keystore" relative-to="jboss.server.config.dir" keystore-password="password" alias="server" key-password="password" generate-self-signed-certificate-host="localhost"/>
</ssl>
</server-identities>
<authentication>
<ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
<username-filter attribute="samaccountname"/>
</ldap>
</authentication>
</security-realm>
{noformat}
2. Define the following outbound connection: -
{noformat}
<outbound-connections>
<ldap name="testLdap" url="ldap://localhost:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="passowrd" />
</outbound-connections>
{noformat}
3. Update the management interfaces to: -
{noformat}
<management-interfaces>
<http-interface security-realm="ldap_security_realm">
<http-upgrade enabled="true"/>
<socket interface="management" port="${jboss.management.http.port:9990}"/>
</http-interface>
</management-interfaces>
{noformat}
The server fails to boot with just the following error: -
{noformat}
[Host Controller] 17:56:40,052 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details.
{noformat}
If the management interface is then updated to reference the ManagementRealm instead the error is now: -
{noformat}
[Host Controller] 18:01:48,595 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
[Host Controller] ("host" => "master"),
[Host Controller] ("core-service" => "management"),
[Host Controller] ("security-realm" => "ldap_security_realm")
[Host Controller] ]) - failure description: {
[Host Controller] "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"jboss.server.config.dir\""],
[Host Controller] "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.core.management.security.realm.ldap_security_realm.key-manager is missing [jboss.server.path.\"jboss.server.config.dir\"]"]
[Host Controller] }
{noformat}
This error is expected as the realm defined in step 1 referenced an invalid path.
I believe the error reporting should come from this method: -
org.jboss.as.controller.ServiceVerificationHelper.execute(OperationContext, ModelNode)
However something seems to have changes with the MSC migration.
This was recently encountered debugging the bug report in https://issues.redhat.com/browse/WFCORE-4820, if you see an error "Multiple CallbackHandlerServices for the same mechanism (PLAIN)" that has been covered by WFCORE-4820.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFCORE-4820) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
by Mark Sanchez (Jira)
[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ]
Mark Sanchez commented on WFCORE-4820:
--------------------------------------
Darran,
Is it possible for you to take our current configuration and map it to Elytron? It looks fairly complicated.
Thanks
Mark Sanchez
> Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4820
> URL: https://issues.redhat.com/browse/WFCORE-4820
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security
> Affects Versions: 10.0.3.Final
> Reporter: Mark Sanchez
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 11.0.0.Beta8
>
>
> error:
> WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> We get an error with the following ldap configuration. This works for version 17.
> <security-realm name="ldap_security_realm">
> <server-identities>
> <ssl>
> <engine enabled-protocols="TLSv1.2"/>
> <keystore path="/opt/app/workload/jboss/ssl_jboss/psftest2s.jboss.keystore" keystore-password="${VAULT::ssl_cert::password::1}"/>
> </ssl>
> </server-identities>
> <authentication>
> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
> <username-filter attribute="samaccountname"/>
> </ldap>
> </authentication>
> </security-realm>
> </security-realms>
> <outbound-connections>
> <ldap name="testLdap" url="ldap://its-ad-ldap.it.test.com:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="${VAULT::ldap_searchdn::password::1}" security-realm="ldap_security_realm"/>
> </outbound-connections>
> <management-interfaces>
> <http-interface security-realm="ldap_security_realm">
> <http-upgrade enabled="true"/>
> <socket interface="management" port="${jboss.management.http.port:9990}"/>
> </http-interface>
> </management-interfaces>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFCORE-4826) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
by James Perkins (Jira)
James Perkins created WFCORE-4826:
-------------------------------------
Summary: Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
Key: WFCORE-4826
URL: https://issues.redhat.com/browse/WFCORE-4826
Project: WildFly Core
Issue Type: Bug
Components: Management, Security
Affects Versions: 10.0.3.Final
Reporter: Mark Sanchez
Assignee: Darran Lofthouse
Fix For: 11.0.0.Beta8
error:
WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
We get an error with the following ldap configuration. This works for version 17.
<security-realm name="ldap_security_realm">
<server-identities>
<ssl>
<engine enabled-protocols="TLSv1.2"/>
<keystore path="/opt/app/workload/jboss/ssl_jboss/psftest2s.jboss.keystore" keystore-password="${VAULT::ssl_cert::password::1}"/>
</ssl>
</server-identities>
<authentication>
<ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
<username-filter attribute="samaccountname"/>
</ldap>
</authentication>
</security-realm>
</security-realms>
<outbound-connections>
<ldap name="testLdap" url="ldap://its-ad-ldap.it.test.com:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="${VAULT::ldap_searchdn::password::1}" security-realm="ldap_security_realm"/>
</outbound-connections>
<management-interfaces>
<http-interface security-realm="ldap_security_realm">
<http-upgrade enabled="true"/>
<socket interface="management" port="${jboss.management.http.port:9990}"/>
</http-interface>
</management-interfaces>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFCORE-4820) Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFCORE-4820?page=com.atlassian.jira.plug... ]
Darran Lofthouse updated WFCORE-4820:
-------------------------------------
Fix Version/s: 11.0.0.Beta8
> Error: WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-4820
> URL: https://issues.redhat.com/browse/WFCORE-4820
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security
> Affects Versions: 10.0.3.Final
> Reporter: Mark Sanchez
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 11.0.0.Beta8
>
>
> error:
> WFLYDM0042: Multiple CallbackHandlerServices for the same mechanism (PLAIN)
> We get an error with the following ldap configuration. This works for version 17.
> <security-realm name="ldap_security_realm">
> <server-identities>
> <ssl>
> <engine enabled-protocols="TLSv1.2"/>
> <keystore path="/opt/app/workload/jboss/ssl_jboss/psftest2s.jboss.keystore" keystore-password="${VAULT::ssl_cert::password::1}"/>
> </ssl>
> </server-identities>
> <authentication>
> <ldap connection="testLdap" base-dn="dc=test,dc=sbc,dc=com" recursive="true">
> <username-filter attribute="samaccountname"/>
> </ldap>
> </authentication>
> </security-realm>
> </security-realms>
> <outbound-connections>
> <ldap name="testLdap" url="ldap://its-ad-ldap.it.test.com:636" search-dn="CN=mxxxxxx,OU=GenericID,OU=testUsers,DC=testServices,DC=test,DC=com" search-credential="${VAULT::ldap_searchdn::password::1}" security-realm="ldap_security_realm"/>
> </outbound-connections>
> <management-interfaces>
> <http-interface security-realm="ldap_security_realm">
> <http-upgrade enabled="true"/>
> <socket interface="management" port="${jboss.management.http.port:9990}"/>
> </http-interface>
> </management-interfaces>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months