[JBoss JIRA] (JBJCA-1343) Account for additional DB2 FATAL connection errors
by Ingo Weiss (JIRA)
Ingo Weiss created JBJCA-1343:
---------------------------------
Summary: Account for additional DB2 FATAL connection errors
Key: JBJCA-1343
URL: https://issues.jboss.org/browse/JBJCA-1343
Project: IronJacamar
Issue Type: Enhancement
Components: Validator
Reporter: Ingo Weiss
Assignee: Ingo Weiss
Various version of pre 11.x DB2 drivers utilize the -99999 error code for a SQLException. Not all -99999 errors are fatal. For those variations that are known to be fatal, a check should be added to treat as such.
One example would be the -99999 error that indicates "Connection is closed"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFLY-7337) Introduce an authorization SPI
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/WFLY-7337?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on WFLY-7337:
---------------------------------
[~dmlloyd] can we close this issue with "Won't Do" ? are you satisfied that we do not introduce these authorization functions into the narayana ?
> Introduce an authorization SPI
> ------------------------------
>
> Key: WFLY-7337
> URL: https://issues.jboss.org/browse/WFLY-7337
> Project: WildFly
> Issue Type: Enhancement
> Components: Transactions
> Reporter: David Lloyd
> Assignee: Amos Feng
>
> We need an SPI that can be invoked to authorize state changes in a transaction. The method(s) should make it clear in some way which operation is being authorized, and it must run from the same thread as the thread which instigates the state change.
> It must be possible to register an implementation of the SPI when the container starts up or acquires the transaction manager.
> The operations that should provide authorization checks include, but are not limited to:
> * begin
> * rollback
> * prepare
> * forget
> * commit (one or two phase)
> * recover
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2549) Elytron, unable to configure Kerberos authentication
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2549?page=com.atlassian.jira.plugi... ]
Kabir Khan updated WFCORE-2549:
-------------------------------
Fix Version/s: 3.0.0.Beta10
(was: 3.0.0.Beta11)
> Elytron, unable to configure Kerberos authentication
> ----------------------------------------------------
>
> Key: WFCORE-2549
> URL: https://issues.jboss.org/browse/WFCORE-2549
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.0.Beta10
>
>
> *User impact:* User can't configure kerberos authentication using Elytron
> *Workaround:* There is no workaround
> *Description:*
> If I try command which worked previously I get error
> {code}
> [standalone@localhost:9990 /] /subsystem=elytron/kerberos-security-factory=a:add(principal=HTTP/localhost@JBOSS.ORG, path=/somewhere, mechanism-oids=["1.2.840.113554.1.2.2","1.3.6.1.5.5.2"])
> {
> "outcome" => "failed",
> "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.IllegalArgumentException",
> "rolled-back" => true
> }
> {code}
> In server.log there is this stacktrace
> {code}
> 15:00:53,476 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("kerberos-security-factory" => "a")
> ]): java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.asPropertyList(ModelValue.java:103)
> at org.jboss.dmr.ModelNode.asPropertyList(ModelNode.java:503)
> at org.wildfly.extension.elytron.KerberosSecurityFactoryDefinition$2.getValueSupplier(KerberosSecurityFactoryDefinition.java:168)
> at org.wildfly.extension.elytron.TrivialAddHandler.performRuntime(TrivialAddHandler.java:77)
> at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:979)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:722)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:441)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1388)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:421)
> at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:217)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:157)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {code}
> Adding optional {{options}} attribute makes command work again
> {code}
> [standalone@localhost:9990 /] /subsystem=elytron/kerberos-security-factory=a:add(principal=HTTP/localhost@JBOSS.ORG, path=/somewhere, mechanism-oids=["1.2.840.113554.1.2.2","1.3.6.1.5.5.2"],options={a=b})
> {"outcome" => "success"}
> {code}
> But after reload, there is error in server log
> {code}
> 18:30:37,430 ERROR [org.jboss.as.controller] (Controller Boot Thread)
> OPVDX001: Validation error in standalone.xml -----------------------------------
> |
> | 365: </kerberos-security-factory>
> | 366: </credential-security-factories>
> | 367: <mappers>
> | ^^^^ 'mappers' isn't an allowed element here
> |
> | Elements allowed here are:
> | audit-logging policy
> | authentication-client providers
> | credential-security-factories sasl
> | credential-stores security-domains
> | dir-contexts security-properties
> | http security-realms
> | mappers tls
> |
> | 368: <constant-permission-mapper name="default-permission-mapper">
> | 369: <permission class-name="org.wildfly.security.auth.permission.LoginPermission"/>
> | 370: <permission class-name="org.wildfly.extension.batch.jberet.deployment.BatchPermission" module="org.wildfly.extension.batch.jberet" target-name="*"/>
> |
> | 'mappers' is allowed in elements:
> | - server > profile > {urn:wildfly:elytron:1.0}subsystem
> | "
> |
> | The primary underlying error message was:
> | > ParseError at [row,col]:[367,13]
> | > Message: WFLYCTL0198: Unexpected element
> | > '{urn:wildfly:elytron:1.0}mappers' encountered
> |
> |-------------------------------------------------------------------------------
> 18:30:37,430 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
> at org.jboss.as.server.ServerService.boot(ServerService.java:376)
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:337)
> at java.lang.Thread.run(Thread.java:745)
> 18:30:37,432 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> {code}
> Attribute {{options}} is marked correctly optional in model.
> {code}
> "options" => {
> "type" => OBJECT,
> "description" => "The Krb5LoginModule additional options.",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (HAWKULARQE-71) Test Hawkular Java Agent
by Hayk Hovsepyan (JIRA)
[ https://issues.jboss.org/browse/HAWKULARQE-71?page=com.atlassian.jira.plu... ]
Hayk Hovsepyan reassigned HAWKULARQE-71:
----------------------------------------
Assignee: Hayk Hovsepyan (was: Michael Foley)
> Test Hawkular Java Agent
> ------------------------
>
> Key: HAWKULARQE-71
> URL: https://issues.jboss.org/browse/HAWKULARQE-71
> Project: Hawkular QE
> Issue Type: Task
> Reporter: Hayk Hovsepyan
> Assignee: Hayk Hovsepyan
> Priority: Minor
>
> There is a new Java Agent (HJA) that you can run in any JVM (including
> but not limited to EAP-based projects). You do so by passing in a
> "-javaagent" command line option to your JVM (e.g. java
> -javaagent=hawkular-javaagent.jar=config=config.yaml -jar my-app.jar
> ...yadda...). There are two additional properties you must set in
> standalone.conf if you want to run it inside an EAP JVM. The README will
> have the details.
> This new HJA is configured with a yaml file that largely mimics all the
> standalone.xml data that HWFA has. There is no ${x} support in the YAML
> file right now.
> This new HJA can talk to any EAP or WildFly server over the DMR management
> API. It can do deployments to your EAP/WildFly servers and monitoring of
> EAP/WildFly subsystems just like HWFA can.
> This new HJA can talk to any JMX server just like HWFA can (it will talk to
> the local MBeanServer or, if remotely monitoring a JMX server, it will talk
> to it over Jolokia/REST API).
> This new HJA can NOT run directly inside of a Host Controller due to
> https://issues.jboss.org/browse/WFCORE-2526 - however, you can run HJA
> externally in its own JVM (e.g. java -jar hawkular-javaagent.jar
> config=config.yaml) and have its config.yaml point to a remote Host
> Controller and you'll get the same functionality.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (WFCORE-2351) There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2351?page=com.atlassian.jira.plugi... ]
Chao Wang commented on WFCORE-2351:
-----------------------------------
Thank your for all the detailed analysis above. In your change, you checked the controller state is not REMOVED before adding any missing dependency. But there are other states like STOPPING and START_FAILED, I guess they are not considered as reasonable state in this particular missing dependency lookup, it's thus safe to only compare with REMOVED here?
> There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2351
> URL: https://issues.jboss.org/browse/WFCORE-2351
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Hynek Švábek
> Assignee: Brian Stansberry
>
> There stuck some required service after unsuccessful command for adding CredentialStore with wrong filled relative-to attribute.
> *Command with wrong filled relative-to attribute*
> {code}
> /subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123}, relative-to=non.exist.path.resource)
> {code}
> *You can see this log.*
> Especially information about New missing/unsatisfied dependencies:is important and it wouldn't be there.
> {code}
> 16:54:18,809 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 8) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "elytron"),
> ("credential-store" => "CredStore108")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.server.path.\"non.exist.path.resource\""],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.credential-store.CredStore108 is missing [jboss.server.path.\"non.exist.path.resource\"]"]
> }
> 16:54:18,810 INFO [org.jboss.as.controller] (management-handler-thread - 8) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.server.path."non.exist.path.resource" (missing) dependents: [service org.wildfly.security.credential-store.CredStore108]
> {code}
> *Now we try process same command without relative-to attribute*
> {code}
> /subsystem=elytron/credential-store=CredStore108:add(uri="cr-store://test/cs108.jceks?create.storage=true", credential-reference={clear-text=pass123})
> {code}
> *Result is success but we can notice this in log:*
> {code}
> 16:55:33,093 INFO [org.jboss.as.controller] (management-handler-thread - 10) WFLYCTL0183: Service status report
> WFLYCTL0185: Newly corrected services:
> service jboss.server.path."non.exist.path.resource" (no longer required)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month