[JBoss JIRA] (ELY-1421) Elytron 1.2 user impacting issues
by Martin Choma (JIRA)
Martin Choma created ELY-1421:
---------------------------------
Summary: Elytron 1.2 user impacting issues
Key: ELY-1421
URL: https://issues.jboss.org/browse/ELY-1421
Project: WildFly Elytron
Issue Type: Tracker
Reporter: Martin Choma
Assignee: Darran Lofthouse
Priority: Trivial
This issue is for tracking changes in Elytron 1.2 which brings new configuration options to users.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (ELY-1170) The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]>
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1170?page=com.atlassian.jira.plugin.s... ]
Martin Choma commented on ELY-1170:
-----------------------------------
So when I want to achieve custom trust-manager I can specify provider-name, but not providers. Providers are "inherited" from ssl-context (or higher). That custom trust-manager must be configured on root element or ssl-context.
So what about adding trust-manager providers resolution possibility? And if not specified "fallback" to root element providers. Or you consider it for unnecessary overkill?
> The TrustManagerFactory should use a Provider from the defined Supplier<Provider[]>
> -----------------------------------------------------------------------------------
>
> Key: ELY-1170
> URL: https://issues.jboss.org/browse/ELY-1170
> Project: WildFly Elytron
> Issue Type: Task
> Components: Authentication Client
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.2.0.Beta8
>
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3371) Upgrade WildFly Elytron Tool to 1.0.4.Final
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3371?page=com.atlassian.jira.plugi... ]
Darran Lofthouse moved JBEAP-13557 to WFCORE-3371:
--------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3371 (was: JBEAP-13557)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
> Upgrade WildFly Elytron Tool to 1.0.4.Final
> -------------------------------------------
>
> Key: WFCORE-3371
> URL: https://issues.jboss.org/browse/WFCORE-3371
> Project: WildFly Core
> Issue Type: Component Upgrade
> Components: Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.7.Final
>
>
> This is just a version sync for the Elytron update.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9454) SecurityContext not injected
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-9454?page=com.atlassian.jira.plugin.... ]
Martin Kouba commented on WFLY-9454:
------------------------------------
For the record - {{javax.security.enterprise.SecurityContext}} comes from [Java EE Security API|https://javaee.github.io/security-api/] which is part of Java EE 8. CDI spec does not define such a built-in bean so it's up to the Security API implementation to provide some.
> SecurityContext not injected
> ----------------------------
>
> Key: WFLY-9454
> URL: https://issues.jboss.org/browse/WFLY-9454
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Security
> Affects Versions: 11.0.0.CR1
> Reporter: Mike Kachalov
>
> 11:49:28,341 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."foo-1.0.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."foo-1.0.ear".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type SecurityContext with qualifiers @Default
> at injection point [BackedAnnotatedField] @Inject private com.foo.bar.facade.impl.UserRegisterFacadeImpl.securityContext
> it's copy issue WELD-2437
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9455) WFLYTX0001: Unable to roll back active transaction thrown for EJB bridge transactions
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-9455?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka updated WFLY-9455:
----------------------------------
Steps to Reproduce:
Could be reproduced with jbosstm quickstart at
https://github.com/jbosstm/quickstart
{code}
export JBOSS_HOME=...
cp $JBOSS_HOME/docs/example/config/standalone-xts.xml standalone/configuration
mvn clean; mvn install -pl XTS/wsat-jta-multi_service -am -Parq -Dtest=BridgeFromJTATest#testCommit
{code}
> WFLYTX0001: Unable to roll back active transaction thrown for EJB bridge transactions
> -------------------------------------------------------------------------------------
>
> Key: WFLY-9455
> URL: https://issues.jboss.org/browse/WFLY-9455
> Project: WildFly
> Issue Type: Bug
> Components: XTS
> Affects Versions: 11.0.0.CR1
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
>
> It happens to get exception
> {code}
> ERROR [org.jboss.as.txn] (default task-12) WFLYTX0003: APPLICATION ERROR: transaction still active in request with status 0
> ERROR [org.jboss.as.txn] (default task-12) WFLYTX0001: Unable to roll back active transaction: javax.transaction.SystemException: WFTXN0032: Rollback not allowed on imported transaction
> at org.wildfly.transaction.client.LocalTransaction.rollbackAndDissociate(LocalTransaction.java:100)
> at org.wildfly.transaction.client.ContextTransactionManager.rollback(ContextTransactionManager.java:83)
> at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.checkTransactionStatus(TransactionRollbackSetupAction.java:137)
> at org.jboss.as.txn.deployment.TransactionRollbackSetupAction.teardown(TransactionRollbackSetupAction.java:67)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1510)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1508)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:326)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:812)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> when using XTS transactions bridged to JTA for EJB handling. This happens on change of integration layer for WFTC in WFLY11.
> The integration issues were already discussed as part of the JBTM-2853.
> Here I hit a trouble of having log filled with the exception mentioned above. This does not cause a functionality trouble but the log is ugly filled with ERRORs.
> The trouble seems to be caused by the fact that transaction is imported on ivocation of WS
> https://github.com/wildfly/wildfly/blob/master/webservices/server-integra...
> but as it was suspended in the integration code before
> https://github.com/jbosstm/narayana/blob/master/txbridge/src/main/java/or...
> now the WFTC holds the notion about the transaction even on call of
> https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java...
> and such transaction is tried to be rollback which is forbidden on WFTC for imported ones and thus at least ERROR msg is written to the log.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3369) CLI to output JSON
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-3369:
----------------------------------------
Summary: CLI to output JSON
Key: WFCORE-3369
URL: https://issues.jboss.org/browse/WFCORE-3369
Project: WildFly Core
Issue Type: Feature Request
Components: CLI
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
Add --output-json and associated XML element.
It impacts:
- Low level operation return value
- echo-dmr displayed output
- run-batch --verbose output
Other commands are not impacted.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months