[JBoss JIRA] (DROOLS-2432) [DMN Designer] Back to from DRD doesn't select proper element in DRG
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2432?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2432:
--------------------------------
Description:
If user navigates back from DRD, the selection in DRG is not updated.
h3. Manual Acceptance Test
- Select *nothing* on canvas, open some context, use back to xyz (/)
- Select *one node* on canvas, open some context, use back to xyz (/)
- Select *multiple nodes* on canvas, open some context, use back to xyz (?)
- Do *unsaved changes* on canvas, open some context, use back to xyz (/)
was:
If user navigates back from DRD, the selection in DRG is not updated.
h3. Manual Acceptance Test
- Select *nothing* on canvas, open some context, use back to xyz (/)
- Select *one node* on canvas, open some context, use back to xyz (/)
- Select *multiple nodes* on canvas, open some context, use back to xyz
- Do *unsaved changes* on canvas, open some context, use back to xyz
> [DMN Designer] Back to from DRD doesn't select proper element in DRG
> --------------------------------------------------------------------
>
> Key: DROOLS-2432
> URL: https://issues.jboss.org/browse/DROOLS-2432
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Minor
>
> If user navigates back from DRD, the selection in DRG is not updated.
> h3. Manual Acceptance Test
> - Select *nothing* on canvas, open some context, use back to xyz (/)
> - Select *one node* on canvas, open some context, use back to xyz (/)
> - Select *multiple nodes* on canvas, open some context, use back to xyz (?)
> - Do *unsaved changes* on canvas, open some context, use back to xyz (/)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2432) [DMN Designer] Back to from DRD doesn't select proper element in DRG
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2432?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2432:
--------------------------------
Description:
If user navigates back from DRD, the selection in DRG is not updated.
h3. Manual Acceptance Test
- Select *nothing* on canvas, open some context, use back to xyz (/)
- Select *one node* on canvas, open some context, use back to xyz
- Select *multiple nodes* on canvas, open some context, use back to xyz
- Do *unsaved changes* on canvas, open some context, use back to xyz
was:
If user navigates back from DRD, the selection in DRG is not updated.
h3. Manual Acceptance Test
- Select *nothing* on canvas, open some context, use back to xyz
- Select *one node* on canvas, open some context, use back to xyz
- Select *multiple nodes* on canvas, open some context, use back to xyz
- Do *unsaved changes* on canvas, open some context, use back to xyz
> [DMN Designer] Back to from DRD doesn't select proper element in DRG
> --------------------------------------------------------------------
>
> Key: DROOLS-2432
> URL: https://issues.jboss.org/browse/DROOLS-2432
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Minor
>
> If user navigates back from DRD, the selection in DRG is not updated.
> h3. Manual Acceptance Test
> - Select *nothing* on canvas, open some context, use back to xyz (/)
> - Select *one node* on canvas, open some context, use back to xyz
> - Select *multiple nodes* on canvas, open some context, use back to xyz
> - Do *unsaved changes* on canvas, open some context, use back to xyz
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2432) [DMN Designer] Back to from DRD doesn't select proper element in DRG
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2432?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2432:
--------------------------------
Description:
If user navigates back from DRD, the selection in DRG is not updated.
h3. Manual Acceptance Test
- Select *nothing* on canvas, open some context, use back to xyz (/)
- Select *one node* on canvas, open some context, use back to xyz (/)
- Select *multiple nodes* on canvas, open some context, use back to xyz
- Do *unsaved changes* on canvas, open some context, use back to xyz
was:
If user navigates back from DRD, the selection in DRG is not updated.
h3. Manual Acceptance Test
- Select *nothing* on canvas, open some context, use back to xyz (/)
- Select *one node* on canvas, open some context, use back to xyz
- Select *multiple nodes* on canvas, open some context, use back to xyz
- Do *unsaved changes* on canvas, open some context, use back to xyz
> [DMN Designer] Back to from DRD doesn't select proper element in DRG
> --------------------------------------------------------------------
>
> Key: DROOLS-2432
> URL: https://issues.jboss.org/browse/DROOLS-2432
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Minor
>
> If user navigates back from DRD, the selection in DRG is not updated.
> h3. Manual Acceptance Test
> - Select *nothing* on canvas, open some context, use back to xyz (/)
> - Select *one node* on canvas, open some context, use back to xyz (/)
> - Select *multiple nodes* on canvas, open some context, use back to xyz
> - Do *unsaved changes* on canvas, open some context, use back to xyz
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2432) [DMN Designer] Back to from DRD doesn't select proper element in DRG
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2432?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2432:
--------------------------------
Description:
If user navigates back from DRD, the selection in DRG is not updated.
h3. Manual Acceptance Test
- Select *nothing* on canvas, open some context, use back to xyz
- Select *one node* on canvas, open some context, use back to xyz
- Select *multiple nodes* on canvas, open some context, use back to xyz
- Do unsaved changes on canvas, open some context, use back to xyz
was:If user navigates back from DRD, the selection in DRG is not updated.
> [DMN Designer] Back to from DRD doesn't select proper element in DRG
> --------------------------------------------------------------------
>
> Key: DROOLS-2432
> URL: https://issues.jboss.org/browse/DROOLS-2432
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Minor
>
> If user navigates back from DRD, the selection in DRG is not updated.
> h3. Manual Acceptance Test
> - Select *nothing* on canvas, open some context, use back to xyz
> - Select *one node* on canvas, open some context, use back to xyz
> - Select *multiple nodes* on canvas, open some context, use back to xyz
> - Do unsaved changes on canvas, open some context, use back to xyz
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2432) [DMN Designer] Back to from DRD doesn't select proper element in DRG
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2432?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2432:
--------------------------------
Description:
If user navigates back from DRD, the selection in DRG is not updated.
h3. Manual Acceptance Test
- Select *nothing* on canvas, open some context, use back to xyz
- Select *one node* on canvas, open some context, use back to xyz
- Select *multiple nodes* on canvas, open some context, use back to xyz
- Do *unsaved changes* on canvas, open some context, use back to xyz
was:
If user navigates back from DRD, the selection in DRG is not updated.
h3. Manual Acceptance Test
- Select *nothing* on canvas, open some context, use back to xyz
- Select *one node* on canvas, open some context, use back to xyz
- Select *multiple nodes* on canvas, open some context, use back to xyz
- Do unsaved changes on canvas, open some context, use back to xyz
> [DMN Designer] Back to from DRD doesn't select proper element in DRG
> --------------------------------------------------------------------
>
> Key: DROOLS-2432
> URL: https://issues.jboss.org/browse/DROOLS-2432
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Minor
>
> If user navigates back from DRD, the selection in DRG is not updated.
> h3. Manual Acceptance Test
> - Select *nothing* on canvas, open some context, use back to xyz
> - Select *one node* on canvas, open some context, use back to xyz
> - Select *multiple nodes* on canvas, open some context, use back to xyz
> - Do *unsaved changes* on canvas, open some context, use back to xyz
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-9892) Upgrade org.apache.santuario.xmlsec to 2.1.1. caused regression in PicketLinkSTS
by Eduardo Martins (JIRA)
[ https://issues.jboss.org/browse/WFLY-9892?page=com.atlassian.jira.plugin.... ]
Eduardo Martins commented on WFLY-9892:
---------------------------------------
[~sgilda] PicketLinkSTS is a quickstart that currently exists only on the eap quickstarts repo, which is now deprecated wrt development. Tomorrow I will workout its cloning to wildfly quickstarts repo, and then create the JIRA wrt this issue on the quickstart.
> Upgrade org.apache.santuario.xmlsec to 2.1.1. caused regression in PicketLinkSTS
> --------------------------------------------------------------------------------
>
> Key: WFLY-9892
> URL: https://issues.jboss.org/browse/WFLY-9892
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 12.0.0.Beta1
> Reporter: Ondrej Lukas
> Assignee: Pedro Igor
> Priority: Blocker
> Attachments: ejb-security-picketlink.zip, ejb-test.jar, picketlink-sts.war, sts-config.properties
>
>
> When token from PicketLink STS is issued and signed then it is not able to be used for authentication through Remoting in WildFly 12 (i.e. it cannot be set as {{remote.connection.main.password}} property which can be used in PicketLink {{org.picketlink.identity.federation.bindings.jboss.auth.SAML2STSLoginModule}}). It seems it is caused by upgrade of org.apache.santuario.xmlsec to version 2.1.1. [1]. When WILDFLY11_HOME/modules/system/layers/base/org/apache/santuario/xmlsec/main/xmlsec-2.0.8.jar is placed to WildFly 12 modules then it works correctly.
> We report it as a blocker since it is regression - application which works correctly on WildFly 11 stops to work on WildFly 12 - users are not able to authenticate through Remoting with signed tokens from PicketLink STS correctly.
> Remoting fails due to following exception:
> {code}
> java.lang.IllegalArgumentException: ELY05131: Invalid ASCII control "0xA"
> at org.wildfly.security.sasl.util.StringPrep.forbidAsciiControl(StringPrep.java:117)
> at org.wildfly.security.sasl.util.StringPrep.encode(StringPrep.java:295)
> at org.wildfly.security.sasl.util.StringPrep.encode(StringPrep.java:196)
> at org.wildfly.security.sasl.plain.PlainSaslClient.evaluateChallenge(PlainSaslClient.java:95)
> at org.wildfly.security.sasl.util.AbstractDelegatingSaslClient.evaluateChallenge(AbstractDelegatingSaslClient.java:54)
> at org.wildfly.security.sasl.util.PrivilegedSaslClient.lambda$evaluateChallenge$0(PrivilegedSaslClient.java:55)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.sasl.util.PrivilegedSaslClient.evaluateChallenge(PrivilegedSaslClient.java:55)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.lambda$handleEvent$1(ClientConnectionOpenListener.java:460)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> It is caused by different formating value of SignatureValue in assertion. In WildFly 11 SignatureValue looks like:
> {code}
> <dsig:SignatureValue xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">nFVkKrXTyYEQ9cwc9OOgySYebEtwzw4alVYP0viXzvqZAUAKtAXEBAfDB8xIOms78twlDdq79MiSvk8OrOdf126Kw/IR8JRn1fYyZ5tsIRcNoTXMgGaTqhrn/HKlLqqqHhVHrJURunqkSzTTxylA2AEPhEDD5Y7hS0W2ZZCeSvuri+PRDSTrRnuedz0yQuHQu1mZ0gjoEFbHh4Wkkn5Ac1R4gmewmmzPud+ZE6Ux4YpeHzQ8rAvZ4bDk6j+eQIRsSxFTLo5RSA3FWN8+lUNV/CSRqBPXsK7QxOaTdBgF+4NXWeExrNJ9SeVFcf9yelvReAtR2JNZ6DUY8u45KtXmLw==</dsig:SignatureValue>
> {code}
> In WildFly 12 it looks like (there are end of lines):
> {code}
> <dsig:SignatureValue xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">cUNpFJIZlLYrBDZtQSTDrq2K6PbnAHyg2qbx/D5FuB4XMjdQ5oxQjkMejLyelnA7s4GFusoLhahl
> qlTOT8UrOyxrR4yYAmJ/e5s+f4gys926+tbiraT/3/wG8wM/Lvcjvk5Ap69zODuRYpypsWfA4jrI
> 7TTBXVPGy8g4KUdnFviUiTuFTc2Ghgxp53AmUuLis/THyP28jE7+28//q8bi/bQrFwHC6tWX67+N
> K1duFCOcQ6IPIKeVrePZz55Ivgl+WWdkF6uYCz5IdMzurhzmeQ3K8DAMIxz/MG67VWJIOnuGNWF7
> nmdye5zd9AFcRsr1XadvZJCbGNfuc89AL5inCg==</dsig:SignatureValue>
> {code}
> [1] https://github.com/wildfly/wildfly/commit/536de514829f2187abf1126c8916a04...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (DROOLS-2431) [DMN Designer] Navigator has not same header height in full screen mode
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2431?page=com.atlassian.jira.plugi... ]
Jozef Marko closed DROOLS-2431.
-------------------------------
Fix Version/s: 7.8.0.Final
Resolution: Cannot Reproduce
[~karreiro] Sorry for an inconvenience. Also for me seems to work fine now. Closing.
> [DMN Designer] Navigator has not same header height in full screen mode
> -----------------------------------------------------------------------
>
> Key: DROOLS-2431
> URL: https://issues.jboss.org/browse/DROOLS-2431
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.8.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Carreiro
> Priority: Trivial
> Fix For: 7.8.0.Final
>
> Attachments: Screenshot from 2018-03-28 08-26-22.png, fedora-chrome.png, fedora-firefox.png, macos-chrome.png, macos-firefox.png, macos-safari.png
>
>
> If DMN Designer enters full screen mode, its header has has different height as navigator, see the attachment. Compare header height in *Decision Navigator* part and *New DMN diagram* part.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (WFLY-9892) Upgrade org.apache.santuario.xmlsec to 2.1.1. caused regression in PicketLinkSTS
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/WFLY-9892?page=com.atlassian.jira.plugin.... ]
Pedro Igor commented on WFLY-9892:
----------------------------------
[~sgilda], you should not get any issue there. The issue we are discussing happens when protecting EJB (using remoting) with SAML, where these assertions are sent via remoting and hit that exception because of the carriage return.
So, yeah. The quickstart is fine.
> Upgrade org.apache.santuario.xmlsec to 2.1.1. caused regression in PicketLinkSTS
> --------------------------------------------------------------------------------
>
> Key: WFLY-9892
> URL: https://issues.jboss.org/browse/WFLY-9892
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 12.0.0.Beta1
> Reporter: Ondrej Lukas
> Assignee: Pedro Igor
> Priority: Blocker
> Attachments: ejb-security-picketlink.zip, ejb-test.jar, picketlink-sts.war, sts-config.properties
>
>
> When token from PicketLink STS is issued and signed then it is not able to be used for authentication through Remoting in WildFly 12 (i.e. it cannot be set as {{remote.connection.main.password}} property which can be used in PicketLink {{org.picketlink.identity.federation.bindings.jboss.auth.SAML2STSLoginModule}}). It seems it is caused by upgrade of org.apache.santuario.xmlsec to version 2.1.1. [1]. When WILDFLY11_HOME/modules/system/layers/base/org/apache/santuario/xmlsec/main/xmlsec-2.0.8.jar is placed to WildFly 12 modules then it works correctly.
> We report it as a blocker since it is regression - application which works correctly on WildFly 11 stops to work on WildFly 12 - users are not able to authenticate through Remoting with signed tokens from PicketLink STS correctly.
> Remoting fails due to following exception:
> {code}
> java.lang.IllegalArgumentException: ELY05131: Invalid ASCII control "0xA"
> at org.wildfly.security.sasl.util.StringPrep.forbidAsciiControl(StringPrep.java:117)
> at org.wildfly.security.sasl.util.StringPrep.encode(StringPrep.java:295)
> at org.wildfly.security.sasl.util.StringPrep.encode(StringPrep.java:196)
> at org.wildfly.security.sasl.plain.PlainSaslClient.evaluateChallenge(PlainSaslClient.java:95)
> at org.wildfly.security.sasl.util.AbstractDelegatingSaslClient.evaluateChallenge(AbstractDelegatingSaslClient.java:54)
> at org.wildfly.security.sasl.util.PrivilegedSaslClient.lambda$evaluateChallenge$0(PrivilegedSaslClient.java:55)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.sasl.util.PrivilegedSaslClient.evaluateChallenge(PrivilegedSaslClient.java:55)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.lambda$handleEvent$1(ClientConnectionOpenListener.java:460)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1481)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1374)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> It is caused by different formating value of SignatureValue in assertion. In WildFly 11 SignatureValue looks like:
> {code}
> <dsig:SignatureValue xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">nFVkKrXTyYEQ9cwc9OOgySYebEtwzw4alVYP0viXzvqZAUAKtAXEBAfDB8xIOms78twlDdq79MiSvk8OrOdf126Kw/IR8JRn1fYyZ5tsIRcNoTXMgGaTqhrn/HKlLqqqHhVHrJURunqkSzTTxylA2AEPhEDD5Y7hS0W2ZZCeSvuri+PRDSTrRnuedz0yQuHQu1mZ0gjoEFbHh4Wkkn5Ac1R4gmewmmzPud+ZE6Ux4YpeHzQ8rAvZ4bDk6j+eQIRsSxFTLo5RSA3FWN8+lUNV/CSRqBPXsK7QxOaTdBgF+4NXWeExrNJ9SeVFcf9yelvReAtR2JNZ6DUY8u45KtXmLw==</dsig:SignatureValue>
> {code}
> In WildFly 12 it looks like (there are end of lines):
> {code}
> <dsig:SignatureValue xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">cUNpFJIZlLYrBDZtQSTDrq2K6PbnAHyg2qbx/D5FuB4XMjdQ5oxQjkMejLyelnA7s4GFusoLhahl
> qlTOT8UrOyxrR4yYAmJ/e5s+f4gys926+tbiraT/3/wG8wM/Lvcjvk5Ap69zODuRYpypsWfA4jrI
> 7TTBXVPGy8g4KUdnFviUiTuFTc2Ghgxp53AmUuLis/THyP28jE7+28//q8bi/bQrFwHC6tWX67+N
> K1duFCOcQ6IPIKeVrePZz55Ivgl+WWdkF6uYCz5IdMzurhzmeQ3K8DAMIxz/MG67VWJIOnuGNWF7
> nmdye5zd9AFcRsr1XadvZJCbGNfuc89AL5inCg==</dsig:SignatureValue>
> {code}
> [1] https://github.com/wildfly/wildfly/commit/536de514829f2187abf1126c8916a04...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months