[JBoss JIRA] (WFLY-3335) JAXB transformer initiation
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-3335?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-3335.
----------------------------
> JAXB transformer initiation
> ---------------------------
>
> Key: WFLY-3335
> URL: https://issues.jboss.org/browse/WFLY-3335
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 8.0.0.Final, 8.1.0.CR1
> Environment: Ubuntu 14.04 with java 7 openjdk
> Reporter: Ghet Ghetolay
> Assignee: David Lloyd
> Priority: Critical
>
> I'm not directly using JAXB and SaxTransformer, it's part of a the [dcm4chee-arc project|https://github.com/dcm4che/dcm4chee-arc] which I tried to use on Wildfly. It's a rather big and complicated project so I've create a test application to illustrate the bug. I've used a JAR-RS application to illustrate the bug (like the original case) but this should not be related to it.
> {code:title=TestRS.java}
> @Path("test")
> public class TestRS {
>
> private static SAXTransformerFactory factory =
> (SAXTransformerFactory) TransformerFactory.newInstance();
>
> @GET
> public Response test(){
> try {
> Templates template = factory.newTemplates(new StreamSource(
> TestRS.class.getResource("json_compact.xsl").toString()));
>
> factory.newTransformerHandler(template);
>
> } catch (TransformerConfigurationException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
> }
>
> return Response.ok().build();
> }
> }
> {code}
> {code:title=json_compact.xsl}
> <?xml version="1.0" encoding="UTF-8"?>
> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
> <xsl:output method="text"/>
> <xsl:template match="/">
> <xsl:text>Test</xsl:text>
> </xsl:template>
> </xsl:stylesheet>
> {code}
> {quote}
> 15:24:48,564 ERROR [stderr] (default task-1) javax.xml.transform.TransformerConfigurationException: Translet class loaded, but unable to create translet instance.
> 15:24:48,564 ERROR [stderr] (default task-1) at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.defineTransletClasses(TemplatesImpl.java:369)
> 15:24:48,565 ERROR [stderr] (default task-1) at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.getTransletInstance(TemplatesImpl.java:383)
> 15:24:48,565 ERROR [stderr] (default task-1) at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.newTransformer(TemplatesImpl.java:418)
> 15:24:48,565 ERROR [stderr] (default task-1) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl.newTransformerHandler(TransformerFactoryImpl.java:1062)
> 15:24:48,565 ERROR [stderr] (default task-1) at __redirected.__TransformerFactory.newTransformerHandler(__TransformerFactory.java:193)
> 15:24:48,566 ERROR [stderr] (default task-1) at test.TestRS.test(TestRS.java:25)
> {quote}
> I've discovered that the initial exception is :
> {quote}
> java.lang.NoClassDefFoundError: com/sun/org/apache/xalan/internal/xsltc/runtime/AbstractTranslet
> {quote}
> Both my test case and dcm4che-arc project works fine on JBoss 7.1.1.Final.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3569) NPE is shown in server shutdown
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3569?page=com.atlassian.jira.plugi... ]
Kabir Khan closed WFCORE-3569.
------------------------------
> NPE is shown in server shutdown
> -------------------------------
>
> Key: WFCORE-3569
> URL: https://issues.jboss.org/browse/WFCORE-3569
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management, IO, Server
> Affects Versions: 4.0.0.Alpha8
> Reporter: Chao Wang
> Assignee: David Lloyd
> Priority: Critical
>
> NullPointerException is shown in server shutdown with an open CLI connection in current WFLY master since WFCORE 4.0.0.Alpha7.
> Start the server and open a CLI connection, then stop server with Ctrl + C. We will see
> {noformat}
> 13:15:09,136 ERROR [org.jboss.threads.errors] (management task-1) Thread Thread[management task-1,5,main] threw an uncaught exception: java.lang.NullPointerException
> at org.jboss.as.server.mgmt.ManagementWorkerService.stopDone(ManagementWorkerService.java:72)
> at org.xnio.XnioWorker$1.run(XnioWorker.java:138)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979)
> at org.jboss.threads.EnhancedQueueExecutor.completeTermination(EnhancedQueueExecutor.java:1755)
> at org.jboss.threads.EnhancedQueueExecutor.tryDeallocateThread(EnhancedQueueExecutor.java:1578)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1393)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> I assign this to David as it seems this is caused by WFCORE-3397 and https://github.com/wildfly/wildfly-core/pull/3072 Please feel free to reassign to correct person.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3321) The jboss.dist system property is not used in testsuite/elytron module
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3321?page=com.atlassian.jira.plugi... ]
Kabir Khan resolved WFCORE-3321.
--------------------------------
Fix Version/s: 3.0.10.Final
Resolution: Done
Just hazarding a guess at the fix version from the info on this issue
> The jboss.dist system property is not used in testsuite/elytron module
> ----------------------------------------------------------------------
>
> Key: WFCORE-3321
> URL: https://issues.jboss.org/browse/WFCORE-3321
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 3.0.3.Final
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Critical
> Fix For: 3.0.10.Final
>
>
> Elytron testsuite module doesn't work correctly with the {{jboss.dist}} system property.
> The {{jboss.dist}} system property is used by QE to run the AS testsuite against the correct bits (e.g. comming from PROD team). The {{testsuite/integration/elytron}} module seems not to be taking this property into account. It seems it always uses output of {{wildfly-server-provisioning-maven-plugin}} to test against.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-3321) The jboss.dist system property is not used in testsuite/elytron module
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3321?page=com.atlassian.jira.plugi... ]
Kabir Khan closed WFCORE-3321.
------------------------------
> The jboss.dist system property is not used in testsuite/elytron module
> ----------------------------------------------------------------------
>
> Key: WFCORE-3321
> URL: https://issues.jboss.org/browse/WFCORE-3321
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 3.0.3.Final
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Critical
> Fix For: 3.0.10.Final
>
>
> Elytron testsuite module doesn't work correctly with the {{jboss.dist}} system property.
> The {{jboss.dist}} system property is used by QE to run the AS testsuite against the correct bits (e.g. comming from PROD team). The {{testsuite/integration/elytron}} module seems not to be taking this property into account. It seems it always uses output of {{wildfly-server-provisioning-maven-plugin}} to test against.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-2527) There is wrong default *relative-to* path for CredentialStore, is set to folder from which we started EAP server.
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2527?page=com.atlassian.jira.plugi... ]
Kabir Khan closed WFCORE-2527.
------------------------------
> There is wrong default *relative-to* path for CredentialStore, is set to folder from which we started EAP server.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2527
> URL: https://issues.jboss.org/browse/WFCORE-2527
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
> Priority: Critical
>
> There is set wrong default *relative-to* path for CredentialStore.
> Default *relative-to* path is set to folder from which we started EAP server.
> e.g.:
> * cd EAP_FOLDER
> * ./bin/standalone.sh
> * relative-to is se to EAP_FOLDER
> or
> * cd EAP_FODER/bin
> * ./standalone.sh
> * relative-to is se to EAP_FOLDER/bin
> *How to reproduce*
> {code}
> /subsystem=elytron/credential-store=cs007:add(uri="cr-store://test/keystorecs007.jceks?create=true", credential-reference= {clear-text=pass123})
> {code}
> {code}
> /subsystem=elytron/credential-store=cs007/alias=newCs007:add(secret-value=Elytron)
> {code}
> Now you can see in EAP_FOLDER (it can be different, see above) keystorecs007.jceks file.
> I would expect this file in data directory of server.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-2503) Legacy security domain used as Elytron security realm does not work in authorization part of aggregate-realm
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2503?page=com.atlassian.jira.plugi... ]
Kabir Khan closed WFCORE-2503.
------------------------------
> Legacy security domain used as Elytron security realm does not work in authorization part of aggregate-realm
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2503
> URL: https://issues.jboss.org/browse/WFCORE-2503
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Priority: Critical
> Attachments: print-roles.war
>
>
> In case when legacy security domain is used as Elytron security realm and is added as authorization realm to aggregate-realm then no roles are assigned to authenticated user.
> I tried to use following legacy security domain:
> {code}
> <security-domain name="legacyDomain" cache-type="default">
> <authentication>
> <login-module code="UsersRoles" flag="required">
> <module-option name="usersProperties" value="/tmp/users.properties"/>
> <module-option name="rolesProperties" value="/tmp/roles.properties"/>
> </login-module>
> </authentication>
> <mapping>
> <mapping-module code="SimpleRoles" type="role">
> <module-option name="admin" value="User"/>
> </mapping-module>
> </mapping>
> </security-domain>
> {code}
> Roles should be assigned from mapping. Since it seems that there is no documentation related to this topic I am not sure whether roles should be assigned also from rolesProperties of UsersRoles login module - it needs to be clarified by developers.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-2490) Multiple CredentialStores with ONE backed credential store file can rewrite values each other.
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2490?page=com.atlassian.jira.plugi... ]
Kabir Khan closed WFCORE-2490.
------------------------------
> Multiple CredentialStores with ONE backed credential store file can rewrite values each other.
> ----------------------------------------------------------------------------------------------
>
> Key: WFCORE-2490
> URL: https://issues.jboss.org/browse/WFCORE-2490
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Peter Skopek
> Priority: Blocker
>
> Multiple CredentialStores with ONE backed credential store file can rewrite values each other.
> *How to reproduce*
> {code}
> /subsystem=elytron/credential-store=credStore001:add(uri="cr-store://test/cs001.jceks?store.password=pass123;create.storage=true")
> /subsystem=elytron/credential-store=credStore001/alias="alias1":add(secret-value=Elytron)
> {code}
> {code}
> /subsystem=elytron/credential-store=credStore002:add(uri="cr-store://test/cs001.jceks?store.password=pass123")
> {code}
> check CS file
> there is "alias1" entry
> {code}
> /subsystem=elytron/credential-store=credStore001/alias="alias2":add(secret-value=Elytron)
> {code}
> check CS file
> there are "alias1" and "alias2" entries
> {code}
> /subsystem=elytron/credential-store=credStore002/alias="alias123":add(secret-value=Elytron)
> {code}
> check CS file
> there are "alias1" and "alias123" entries".
> *NOTE*
> It is problem, because we have one backed file. In memory we have right values for all Credential Stores, but after restart we can lost new entries.
> In my opinion reason for this behaviour is:
> We have CS loaded in memory and when we add new alias to CS then we save whole CS from memory to file.
> We can set CS as non-modifiable when we use same backed file for CredentialStore but we must find better default behaviour.
> *My suggestion for default behaviour*
> When we want to add new alias to CredentialStore we can do this:
> # refresh CS from file (and this file lock)
> # add new alias to CS
> # save CS to file
> # unlock file
> *But there is posible problem with performance....*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months
[JBoss JIRA] (WFCORE-2485) CS tool, add prompt when --password is missing
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2485?page=com.atlassian.jira.plugi... ]
Kabir Khan closed WFCORE-2485.
------------------------------
> CS tool, add prompt when --password is missing
> ----------------------------------------------
>
> Key: WFCORE-2485
> URL: https://issues.jboss.org/browse/WFCORE-2485
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Blocker
> Labels: credential-store
>
> Use case:
> - User have automation script using cs tool and user don't want to have password stored in file.
> - User don't want credential store password to be stored in shell history after execution.
> - User don't want credential store password to be listed in {{ps -aux}} output.
> There have to be possibility to omit --password attribute. When omitting --password attribute user interaction prompt should follow with possibility to input password.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 6 months