July 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-431) Arquillian-based integration tests

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-431: ------------------------------ Fix Version/s: 0.6.0 > Arquillian-based integration tests > ---------------------------------- > > Key: SRAMP-431 > URL: https://issues.jboss.org/browse/SRAMP-431 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.6.0 > > > Create a new s-ramp-test module to contain all integration tests. Thoughts: > - 1 central ant script, executed by the POM, should be in charge of downloading the Jetty and and Tomcat distros, then unpacking them. Arquillian would then use them in a "managed mode." > - The ant script will eventually be in charge of downloading EAP as well, but not until we have CI hardware within the RH network. Until then, we'll need to do something similar to RTGov's current tests: require the distro be manually downloaded and unpacked, then set $JBOSS_HOME > - Fuse should be run in embedded mode. > - No tests should run by default. Hide all behind container-specific profiles, enabled only on the CI job(s). > - Include a simple s-ramp-client based test to at least ensure the app comes up, auth works, and uploading/querying works. > - Pull in any functional tests from the other modules requiring the server to be spun-up. Leave behind only pure *unit* tests. > The work-in-progress: https://github.com/brmeyer/s-ramp/compare/integration-tests -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-436) Overlord SSO (IDP/SP) needs to have SAML assertion sigs enabled by default

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-436?page=com.atlassian.jira.plugin.... ] Eric Wittmann closed SRAMP-436. ------------------------------- > Overlord SSO (IDP/SP) needs to have SAML assertion sigs enabled by default > -------------------------------------------------------------------------- > > Key: SRAMP-436 > URL: https://issues.jboss.org/browse/SRAMP-436 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Currently we're not signing the saml assertions. We need to do that. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-436) Overlord SSO (IDP/SP) needs to have SAML assertion sigs enabled by default

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-436?page=com.atlassian.jira.plugin.... ] Eric Wittmann resolved SRAMP-436. --------------------------------- Resolution: Done > Overlord SSO (IDP/SP) needs to have SAML assertion sigs enabled by default > -------------------------------------------------------------------------- > > Key: SRAMP-436 > URL: https://issues.jboss.org/browse/SRAMP-436 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Currently we're not signing the saml assertions. We need to do that. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-257) Allow parametrization of (not only) MVEL scripts in EPN

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/RTGOV-257?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on RTGOV-257: ----------------------------------------------- Gary Brown <gbrown(a)redhat.com> changed the Status of [bug 1000312|https://bugzilla.redhat.com/show_bug.cgi?id=1000312] from NEW to ASSIGNED > Allow parametrization of (not only) MVEL scripts in EPN > ------------------------------------------------------- > > Key: RTGOV-257 > URL: https://issues.jboss.org/browse/RTGOV-257 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Event Processor > Affects Versions: 1.0.0.Final > Reporter: Jiri Pechanec > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > EPN allows to use MVEL or Java class as processor or predicate. > It would be great addition to re-usability of the scripts and classe if it > would be possible to pass a set of parameters from epn.json to the > processor/evaluator for the instance. > It could work in a similar way as injection of services - via EPNContext. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-526) Use parameterisation to make SLA EPN customisable

by Gary Brown (JIRA)

Gary Brown created RTGOV-526: -------------------------------- Summary: Use parameterisation to make SLA EPN customisable Key: RTGOV-526 URL: https://issues.jboss.org/browse/RTGOV-526 Project: RTGov (Run Time Governance) Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final Try to pass in a list of response time to situation status values, and change the rule to loop through to determine if a situation should be created. The information should be configured in highest response time order. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-257) Allow parametrization of (not only) MVEL scripts in EPN

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-257?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-257: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/152 > Allow parametrization of (not only) MVEL scripts in EPN > ------------------------------------------------------- > > Key: RTGOV-257 > URL: https://issues.jboss.org/browse/RTGOV-257 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Event Processor > Affects Versions: 1.0.0.Final > Reporter: Jiri Pechanec > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > EPN allows to use MVEL or Java class as processor or predicate. > It would be great addition to re-usability of the scripts and classe if it > would be possible to pass a set of parameters from epn.json to the > processor/evaluator for the instance. > It could work in a similar way as injection of services - via EPNContext. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-257) Allow parametrization of (not only) MVEL scripts in EPN

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-257?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-257. ------------------------------ Resolution: Done > Allow parametrization of (not only) MVEL scripts in EPN > ------------------------------------------------------- > > Key: RTGOV-257 > URL: https://issues.jboss.org/browse/RTGOV-257 > Project: RTGov (Run Time Governance) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Event Processor > Affects Versions: 1.0.0.Final > Reporter: Jiri Pechanec > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > EPN allows to use MVEL or Java class as processor or predicate. > It would be great addition to re-usability of the scripts and classe if it > would be possible to pass a set of parameters from epn.json to the > processor/evaluator for the instance. > It could work in a similar way as injection of services - via EPNContext. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-436) Overlord SSO (IDP/SP) needs to have SAML assertion sigs enabled by default

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-436?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-436: -------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/85, https://github.com/Governance/s-ramp/pull/455, https://github.com/Governance/dtgov/pull/206, https://github.com/Governance/rtgov/pull/151, https://github.com/bpmc/bpm-console/pull/36 (was: https://github.com/Governance/overlord-commons/pull/85, https://github.com/Governance/s-ramp/pull/455, https://github.com/Governance/dtgov/pull/206, https://github.com/Governance/rtgov/pull/151) > Overlord SSO (IDP/SP) needs to have SAML assertion sigs enabled by default > -------------------------------------------------------------------------- > > Key: SRAMP-436 > URL: https://issues.jboss.org/browse/SRAMP-436 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Currently we're not signing the saml assertions. We need to do that. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-436) Overlord SSO (IDP/SP) needs to have SAML assertion sigs enabled by default

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-436?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-436: -------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/85, https://github.com/Governance/s-ramp/pull/455, https://github.com/Governance/dtgov/pull/206, https://github.com/Governance/rtgov/pull/151 (was: https://github.com/Governance/overlord-commons/pull/85, https://github.com/Governance/s-ramp/pull/455, https://github.com/Governance/dtgov/pull/206) > Overlord SSO (IDP/SP) needs to have SAML assertion sigs enabled by default > -------------------------------------------------------------------------- > > Key: SRAMP-436 > URL: https://issues.jboss.org/browse/SRAMP-436 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Currently we're not signing the saml assertions. We need to do that. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-507) Modify way the snapshot artifacts are stored in s-ramp

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-507?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated SRAMP-507: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1060773 > Modify way the snapshot artifacts are stored in s-ramp > ------------------------------------------------------ > > Key: SRAMP-507 > URL: https://issues.jboss.org/browse/SRAMP-507 > 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 > > > Include a property mvn.snapshot.timestamp (in case the name contains the timestamp) > When deploying a snapshot artifact, maven will include a timestamp in the filename. The maven repository facade *and* the s-ramp wagon should be updated to store this timestamp info in a new s-ramp property (see above). In addition, the s-ramp wagon should no longer *ever* attempt to update an artifact. Here is what it should do: > h4. Release artifacts > * If this artifact (GAV) already exists in s-ramp, fail > * If this artifact doesn't yet exist, add it > h4. Snapshot artifacts > * If this artifact (GAV + timestamp) already exists in s-ramp, fail > * If this artifact doesn't yet exist, add it along with its timestamp information -- This message was sent by Atlassian JIRA (v6.2.6#6264)

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 July 2014