[JBoss JIRA] (AS7-5245) vault shared key should be salted
by Gernot P (JIRA)
Gernot P created AS7-5245:
-----------------------------
Summary: vault shared key should be salted
Key: AS7-5245
URL: https://issues.jboss.org/browse/AS7-5245
Project: Application Server 7
Issue Type: Feature Request
Components: Security
Affects Versions: 7.1.1.Final
Reporter: Gernot P
Assignee: Anil Saldhana
Actual behaviour:
(1) create a vault entry with
vault attribute value: xxx
vault block: y1
vault attribute name: z1
(2) create another vault entry with
vault attribute value: xxx
vault block: y2
vault attribute name: z2
and you see that vault shared key is the same for entry 1 and entry 2
feature request:
two vault entries with same attribute value but different block names and attribute names should have different shared keys
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] (AS7-5067) CLONE - CLI deploy with --name fails to deploy subdeployments
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/AS7-5067?page=com.atlassian.jira.plugin.s... ]
Alexey Loubyansky resolved AS7-5067.
------------------------------------
Resolution: Rejected
The name is expected to have a recognized suffix, this is the contract for the deployers. I.e.
deploy simpleejb3.ear --name=b.ear
will work in this case.
> CLONE - CLI deploy with --name fails to deploy subdeployments
> -------------------------------------------------------------
>
> Key: AS7-5067
> URL: https://issues.jboss.org/browse/AS7-5067
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Tom Fonteyne
> Assignee: Alexey Loubyansky
> Priority: Minor
> Attachments: simpleejb3.ear
>
>
> I have an ear file with inside a jar file with an ejb.
> Use the CLI to deploy with:
> > deploy simpleejb3.ear
> In the console log:
> 12:22:42,130 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "simpleejb3.ear"
> 12:22:42,174 INFO [org.jboss.as.server.deployment] (MSC service thread 1-16) JBAS015876: Starting deployment of "simpleejb3-ejb.jar"
> 12:22:42,293 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-5) JNDI bindings for session bean named sbean in deployment unit subdeployment "simpleejb3-ejb.jar" of deployment "simpleejb3.ear" are as follows:
> java:global/simpleejb3/simpleejb3-ejb/sbean!tf.sbeanLocal
> java:app/simpleejb3-ejb/sbean!tf.sbeanLocal
> java:module/sbean!tf.sbeanLocal
> java:global/simpleejb3/simpleejb3-ejb/sbean!tf.sbeanRemote
> java:app/simpleejb3-ejb/sbean!tf.sbeanRemote
> java:module/sbean!tf.sbeanRemote
> java:jboss/exported/simpleejb3/simpleejb3-ejb/sbean!tf.sbeanRemote
> and the bean will work.
> Now undeploy fully (+ restarted) and deploy again with:
> > deploy simpleejb3.ear --name=b
> and the log :
> 12:23:41,300 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "b"
> 12:23:41,431 INFO [org.jboss.as.osgi] (MSC service thread 1-4) JBAS011907: Register module: Module "deployment.b:main" from Service Module Loader
> 12:23:41,598 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "b"
> A test showed that the EJB was indeed not deployed/accessible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months