September 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-564) Fuse Deployment, Class Not found exception org.overlord.sramp.events

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-564?page=com.atlassian.jira.plugin.... ] David virgil naranjo updated SRAMP-564: --------------------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/483 > Fuse Deployment, Class Not found exception org.overlord.sramp.events > -------------------------------------------------------------------- > > Key: SRAMP-564 > URL: https://issues.jboss.org/browse/SRAMP-564 > Project: S-RAMP > Issue Type: Bug > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > There is an exception in Fuse Fabric related with two new packages included in s-ramp: > java.lang.NoClassDefFoundError: org/overlord/sramp/events/EventProducerFactory > the packages to be included in the pom.xml of s-ramp-server are > org/overlord/sramp/events and org/overlord/sramp/events.jms -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-564) Fuse Deployment, Class Not found exception org.overlord.sramp.events

by David virgil naranjo (JIRA)

David virgil naranjo created SRAMP-564: ------------------------------------------ Summary: Fuse Deployment, Class Not found exception org.overlord.sramp.events Key: SRAMP-564 URL: https://issues.jboss.org/browse/SRAMP-564 Project: S-RAMP Issue Type: Bug Reporter: David virgil naranjo Assignee: David virgil naranjo There is an exception in Fuse Fabric related with two new packages included in s-ramp: java.lang.NoClassDefFoundError: org/overlord/sramp/events/EventProducerFactory the packages to be included in the pom.xml of s-ramp-server are org/overlord/sramp/events and org/overlord/sramp/events.jms -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-542) If a SNAPSHOT artifact does not include a timestamp, have DeployCommand generate it

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-542?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-542. ------------------------------- Resolution: Done > If a SNAPSHOT artifact does not include a timestamp, have DeployCommand generate it > ----------------------------------------------------------------------------------- > > Key: SRAMP-542 > URL: https://issues.jboss.org/browse/SRAMP-542 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: David virgil naranjo > Priority: Minor > Fix For: 0.6.0 > > > Low priority -- we shouldn't consider this until 0.6. > DeployCommand is currently assuming a SNAPSHOT artifact includes a timestamp. But, if I'm using the CLI to deploy a locally built artifact, it won't. Consider automatically generating a timestamp if it's missing so that I can upload new snapshots. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-561) Support Fuse JMS

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-561?page=com.atlassian.jira.plugin.... ] David virgil naranjo commented on SRAMP-561: -------------------------------------------- [16:47] <chirino> yeah.. so I'd just use new ActiveMQConnectionFactory(url) [16:47] <chirino> and make url configurable. [16:47] <chirino> when in fabric, configure url="fabric://default" [16:48] <chirino> and the client will connect to a random broker in the default group. [16:48] <chirino> if not in fabric, configure url to be something like: "failover://(tcp://localhost:61616)" [16:48] <chirino> where your explictly configuring where the broker is running. [16:50] <virchete> by default that is the port [16:50] <virchete> 61616 [16:50] <chirino> yeah [16:50] <virchete> ok man [16:50] <virchete> very helpful [16:51] <virchete> if anytime you have a doubt about jboss overlord project [16:51] <virchete> come to me [16:51] <virchete> xD [16:51] <chirino> ok thx! > Support Fuse JMS > ---------------- > > Key: SRAMP-561 > URL: https://issues.jboss.org/browse/SRAMP-561 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: David virgil naranjo > Fix For: 0.6.0 > > > SRAMP-433 created JMS events within S-RAMP. For Tomcat, Jetty, and standalone EAP, we use an embedded ActiveMQ broker. For standalone-full EAP, we re-use the existing HornetQ JMS and JNDI resources. > Supposedly, Fuse provides ActiveMQ out-of-the-box. We should re-use that, rather than relying on the embedded broker. Investigate and figure out a way to add the JMS resources during S-RAMP installation, similar to the new configureJMS-jboss-eap-6.xslt. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-527) Add overlord.properties to fuse fabric profile

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-527?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-527. ------------------------------- Fix Version/s: 0.5.0.Final Resolution: Done > Add overlord.properties to fuse fabric profile > ---------------------------------------------- > > Key: SRAMP-527 > URL: https://issues.jboss.org/browse/SRAMP-527 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 0.5.0.Final > > > Add the overlord.properties file to the overlord fuse fabric profile. > Try the deployment in fuse fabric. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-527) Add overlord.properties to fuse fabric profile

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-527?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-527. ----------------------------- > Add overlord.properties to fuse fabric profile > ---------------------------------------------- > > Key: SRAMP-527 > URL: https://issues.jboss.org/browse/SRAMP-527 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 0.5.0.Final > > > Add the overlord.properties file to the overlord fuse fabric profile. > Try the deployment in fuse fabric. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-380) Passwords in clear text when running in Fuse 6.1

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-380?page=com.atlassian.jira.plugin.... ] Brett Meyer resolved SRAMP-380. ------------------------------- Resolution: Done > Passwords in clear text when running in Fuse 6.1 > ------------------------------------------------ > > Key: SRAMP-380 > URL: https://issues.jboss.org/browse/SRAMP-380 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.6.0 > > > When we install into JBoss EAP we make sure that we don't have any clear text passwords in any configuration files. This is made possible by using the Vault, which allows us to store passwords in the vault and then refer to those vault locations from our config files. > I don't know if there is something similar to be done in Fuse 6.1 > In addition, the login credentials for supported users in EAP are not stored in clear text (the EAP Application Realm config files store an encrypted version of the passwords). > In Fuse 6.1 we are storing the login user credentials in a users.properties file in clear text. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-128) Encrypt the passwords in overlord.properties

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-128?page=com.atlassian.jira.plug... ] Brett Meyer closed OVERLORD-128. -------------------------------- > Encrypt the passwords in overlord.properties > -------------------------------------------- > > Key: OVERLORD-128 > URL: https://issues.jboss.org/browse/OVERLORD-128 > Project: Overlord > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: Overlord-Commons-2.0.7.Final > > > The password properties inside of the overlord.properties file should be encrypted in the properties file and then decrypted by the application whenever the encrypted properties are used. > Properties to be encrypted: > overlord.auth.saml-key-alias-password > overlord.auth.saml-keystore-password > It can be used as synchronous security encrypting algorithm, the AES Encrypting algorithm. > It can be used commons-coded. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-128) Encrypt the passwords in overlord.properties

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-128?page=com.atlassian.jira.plug... ] Brett Meyer resolved OVERLORD-128. ---------------------------------- Fix Version/s: Overlord-Commons-2.0.7.Final Resolution: Done > Encrypt the passwords in overlord.properties > -------------------------------------------- > > Key: OVERLORD-128 > URL: https://issues.jboss.org/browse/OVERLORD-128 > Project: Overlord > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: Overlord-Commons-2.0.7.Final > > > The password properties inside of the overlord.properties file should be encrypted in the properties file and then decrypted by the application whenever the encrypted properties are used. > Properties to be encrypted: > overlord.auth.saml-key-alias-password > overlord.auth.saml-keystore-password > It can be used as synchronous security encrypting algorithm, the AES Encrypting algorithm. > It can be used commons-coded. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-538) password encryption in overlord commons

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-538?page=com.atlassian.jira.plugin.... ] Brett Meyer closed SRAMP-538. ----------------------------- > password encryption in overlord commons > --------------------------------------- > > Key: SRAMP-538 > URL: https://issues.jboss.org/browse/SRAMP-538 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: David virgil naranjo > Assignee: David virgil naranjo > Fix For: 0.5.0.Final > > > Adapt the installers and distribution packages to the new changes done in overlord commons to encrypt the overlord.properties passwords: > Related overlord-commons jira: > https://issues.jboss.org/browse/OVERLORD-128 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues September 2014