September 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (OVERLORD-142) Not all required overlord properties are created if file already exists in fuse

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-142?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated OVERLORD-142: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1146591 > Not all required overlord properties are created if file already exists in fuse > ------------------------------------------------------------------------------- > > Key: OVERLORD-142 > URL: https://issues.jboss.org/browse/OVERLORD-142 > Project: Overlord > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: Overlord-Commons-2.0.8.Final > > > The properties: > overlord.auth.saml-key-alias=overlord > overlord.auth.saml-keystore=${sys\:karaf.home}/etc/overlord-saml.keystore > are not created by the overlord:generatesamlkeystore command if the file already exists. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (OVERLORD-117) Pull Fabric profile tasks out of overlord-commons-dist-fuse6 and into a new overlord-commons-dist-fabric-profile

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/OVERLORD-117?page=com.atlassian.jira.plug... ] RH Bugzilla Integration updated OVERLORD-117: --------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1146591 > Pull Fabric profile tasks out of overlord-commons-dist-fuse6 and into a new overlord-commons-dist-fabric-profile > ---------------------------------------------------------------------------------------------------------------- > > Key: OVERLORD-117 > URL: https://issues.jboss.org/browse/OVERLORD-117 > Project: Overlord > Issue Type: Task > Reporter: Brett Meyer > Assignee: David virgil naranjo > Fix For: Overlord-Commons-2.0.9.Final > > > Similar to S-RAMP, DTGov, and RTGov, pull the Fabric profiles into a separate dist within overlord-commons. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-570) Improve s-ramp commands for Fuse/Fabric

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-570?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated SRAMP-570: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1146591 > Improve s-ramp commands for Fuse/Fabric > --------------------------------------- > > Key: SRAMP-570 > URL: https://issues.jboss.org/browse/SRAMP-570 > Project: S-RAMP > Issue Type: Enhancement > Reporter: David virgil naranjo > Assignee: David virgil naranjo > > For Fuse: > 1.) Make the password argument optional > 2.) If no Overlord installation has been attempted (the existence of overlord.properties in FUSE/etc is a good test), fail if no password is provided > 3.) If a password is provided, but overlord.properties already exists, print what Gary mentioned: an installation already exists, re-using those credentials, but the "overlord:changePassword" command is available > 4.) Create overlord:changePassword. It would regenerate the keystore and update any applicable *.properties values > Modify/Add commands to deploy in Fuse Fabric. Create new commands. They would be like fuse commands, but starting by fabric : fabric:overlord:s-ramp:configure -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-569) Create maven plugin to merge .properties files

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-569?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated SRAMP-569: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1146591 > Create maven plugin to merge .properties files > ---------------------------------------------- > > Key: SRAMP-569 > URL: https://issues.jboss.org/browse/SRAMP-569 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: David virgil naranjo > Fix For: 0.6.0 > > > SRAMP-566 removes Fuse from s-ramp-installer. Instead, Fuse configuration is scripted through s-ramp-karaf-commands. That project currently controls its own versions of sramp.properties, sramp-ui.properties, etc. This was originally done since some of the values are static and *specific* to Fuse. > However, several values remain unchanged when compared to the other platforms. It would be better if s-ramp-karaf-commands/pom.xml was able to pull ../s-ramp-installer/**/*.properties and merge it with .properties still controlled in s-ramp-karaf-commands. However, the s-ramp-karaf-commands version would contain *only* the Fuse specific values. > Essentially, we're relying on s-ramp-installer's versions during buildtime, but overriding with any necessary Fuse values in s-ramp-karaf-commands. A custom Maven plugin to support this should be incredibly easy. Use Java's Properties, load the first version, then load and override with the 2nd. See http://beardedgeeks.googlecode.com/svn/docs/maven-merge-properties-plugin... for inspiration. > Note that this is also needed for overlord-commons-karaf-commands (configure.dtd, overlord.properties, etc.) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-380?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated SRAMP-380: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1146591 > 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 > 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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-566) Remove Fuse from installer and replace with new Karaf commands

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-566?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated SRAMP-566: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1146591 > Remove Fuse from installer and replace with new Karaf commands > -------------------------------------------------------------- > > Key: SRAMP-566 > URL: https://issues.jboss.org/browse/SRAMP-566 > Project: S-RAMP > Issue Type: Enhancement > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Rather than continue to support Fuse from within the installer, instead create Karaf command(s) to handle it all. Each project will have at least it's own overlord:[project]:configure. We'll also need to kick off overlord-commons GenerateSamlKeystoreCommand somehow, either by creating a central overlord:commons:configure (not sure that's best) or running it from *all* other projects' configure commands (and ensure it's only run once). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-545) Provide ability to delete ontology via UI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-545?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated SRAMP-545: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1146588 > Provide ability to delete ontology via UI > ----------------------------------------- > > Key: SRAMP-545 > URL: https://issues.jboss.org/browse/SRAMP-545 > Project: S-RAMP > Issue Type: Enhancement > Components: UI > Affects Versions: 0.5.0.Final > Reporter: Stefan Bunciak > Assignee: Brett Meyer > Priority: Critical > Fix For: 0.6.0 > > > There is no way how to delete ontology in S-RAMP UI. One would expect such functionality in Ontology Management section. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-510) Situation state transition to Close causes resolutionState and assignedTo properties to be cleared

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-510?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-510. ------------------------------ Resolution: Done Changed button label and associated method names from 'Close' to 'Unassign' to better reflect what it was performing. > Situation state transition to Close causes resolutionState and assignedTo properties to be cleared > -------------------------------------------------------------------------------------------------- > > Key: RTGOV-510 > URL: https://issues.jboss.org/browse/RTGOV-510 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Currently when transitioning a Situation to the Closed state causes the 'resolutionState' and 'assignedTo' properties to be cleared. > This is the same state as when the Situation is first created and therefore creates an ambiguity regarding whether the situation has been dealt with. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-510) Situation state transition to Close causes resolutionState and assignedTo properties to be cleared

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-510?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-510: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/209 > Situation state transition to Close causes resolutionState and assignedTo properties to be cleared > -------------------------------------------------------------------------------------------------- > > Key: RTGOV-510 > URL: https://issues.jboss.org/browse/RTGOV-510 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Currently when transitioning a Situation to the Closed state causes the 'resolutionState' and 'assignedTo' properties to be cleared. > This is the same state as when the Situation is first created and therefore creates an ambiguity regarding whether the situation has been dealt with. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-510) Situation state transition to Close causes resolutionState and assignedTo properties to be cleared

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-510?page=com.atlassian.jira.plugin.... ] Gary Brown reassigned RTGOV-510: -------------------------------- Assignee: Gary Brown (was: Michael Clay) > Situation state transition to Close causes resolutionState and assignedTo properties to be cleared > -------------------------------------------------------------------------------------------------- > > Key: RTGOV-510 > URL: https://issues.jboss.org/browse/RTGOV-510 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > Currently when transitioning a Situation to the Closed state causes the 'resolutionState' and 'assignedTo' properties to be cleared. > This is the same state as when the Situation is first created and therefore creates an ambiguity regarding whether the situation has been dealt with. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 9 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