April 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-212) Support property expansion in CLI command files

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-212?page=com.atlassian.jira.plugin.... ] David virgil naranjo resolved SRAMP-212. ---------------------------------------- Resolution: Done > Support property expansion in CLI command files > ----------------------------------------------- > > Key: SRAMP-212 > URL: https://issues.jboss.org/browse/SRAMP-212 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Shell > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.5.0 - API Management > > > Currently the CLI (sramp shell) supports the ability to pass it a file containing a list of commands to execute. This should be enhanced to support property expansion (standard Ant format), which would allow for more powerful/useful operation when integrating with e.g. Ant. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-384) Add validation for password in overlord commons installer

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-384?page=com.atlassian.jira.plugin.... ] David virgil naranjo resolved SRAMP-384. ---------------------------------------- Resolution: Done > Add validation for password in overlord commons installer > --------------------------------------------------------- > > Key: SRAMP-384 > URL: https://issues.jboss.org/browse/SRAMP-384 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.5.0 - API Management > > > Currently the overlord commons installer is responsible for doing all security related work. This includes creating the overlord 'admin' user and configured a password for this user. The installer prompts the user for this password and then passes whatever the user entered to the JBoss EAP add-user utility. This utility will fail if the password does not meet certain standards. However, the utility fails without failing the overall install. > The installer should do its own validation of the password entered by the user so that this silent failure doesn't happen. Also note that the password input and validation should happen before anything else security related gets installed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-388) Use jboss version of javax.servlet GAV consistently

by David virgil naranjo (JIRA)

[ https://issues.jboss.org/browse/SRAMP-388?page=com.atlassian.jira.plugin.... ] David virgil naranjo resolved SRAMP-388. ---------------------------------------- Fix Version/s: 0.5.0 - API Management Resolution: Done > Use jboss version of javax.servlet GAV consistently > --------------------------------------------------- > > Key: SRAMP-388 > URL: https://issues.jboss.org/browse/SRAMP-388 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > Fix For: 0.5.0 - API Management > > > EAP uses the GAV > {code} > <dependency> > <groupId>org.jboss.spec.javax.servlet</groupId> > <artifactId>jboss-servlet-api_3.0_spec</artifactId> > </dependency> > {code} > rather than > {code} > <dependency> > <groupId>javax.servlet</groupId> > <artifactId>servlet-api</artifactId> > </dependency> > {code} > This GAV is also available in the community BOM. > We need to remove all references to the javax.servlet:servlet-api dependency in all Overlord projects (s-ramp, dtgov, overlord-commons, etc). Anywhere we reference that GAV please change it to org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-415) ElasticSearch Activity Store implementation

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-415: ---------------------------------- I guess the main question would be how the ActivityUnit is deserialized - does it need to be reconstructed in code, or does the mapping provide support for decomposing and then composing back the original full document? >From a query perspective, I guess the AU would have its id and origin information - and the ATs for the AU would have the AU id as a foreign key that could be used to tie them back to the same unit? > ElasticSearch Activity Store implementation > ------------------------------------------- > > Key: RTGOV-415 > URL: https://issues.jboss.org/browse/RTGOV-415 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > > Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative. > If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times). > ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional. > The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-415) ElasticSearch Activity Store implementation

by ivan mckinley (JIRA)

[ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.... ] ivan mckinley edited comment on RTGOV-415 at 4/28/14 6:37 PM: -------------------------------------------------------------- Gary, I'm testing a different type of ES document mapping. Was - ActivityUnit = flat document with ActivityType as nested objects Now - ActivityUnit = has many ActivityType child type documents. The nested object approach was difficult to achieve the functionality outlined by the ActivityStore interface. This results in kibana would have work with two documents . the activityUnit and the activityType. Would be interested in your opinion on this as this would impact how kibana displays the AU nd AT data was (Author: imckinle): Gary, I'm testing a different type ES mappings. Was - ActivityUnit = flat document with ActivityType as nested objects Now - ActivityUnit = has many ActivityType child type documents. The nested object approach was difficult to achieve the functionality outlined by the ActivityStore interface. This results in kibana would have work with two documents . the activityUnit and the activityType. Would be interested in your opinion on this as this would impact how kibana displays the AU nd AT data > ElasticSearch Activity Store implementation > ------------------------------------------- > > Key: RTGOV-415 > URL: https://issues.jboss.org/browse/RTGOV-415 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > > Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative. > If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times). > ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional. > The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-415) ElasticSearch Activity Store implementation

by ivan mckinley (JIRA)

[ https://issues.jboss.org/browse/RTGOV-415?page=com.atlassian.jira.plugin.... ] ivan mckinley commented on RTGOV-415: ------------------------------------- Gary, I'm testing a different type ES mappings. Was - ActivityUnit = flat document with ActivityType as nested objects Now - ActivityUnit = has many ActivityType child type documents. The nested object approach was difficult to achieve the functionality outlined by the ActivityStore interface. This results in kibana would have work with two documents . the activityUnit and the activityType. Would be interested in your opinion on this as this would impact how kibana displays the AU nd AT data > ElasticSearch Activity Store implementation > ------------------------------------------- > > Key: RTGOV-415 > URL: https://issues.jboss.org/browse/RTGOV-415 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: ivan mckinley > Fix For: 2.0.0.Final > > > Although it is not currently clear whether organisations would rely on ElasticSearch as a database for their activity information, it will be good to be able to offer it as an alternative. > If configured, then it will store the ActivityUnit, and any subsequent EPN can be used to store the derived information (e.g. situations and response times). > ElasticSearch has improved its support for backup/restore, so could potentially be used as a primary db for this type of information - although it is not transactional. > The module should be defined in modules/activity-management/activity-store-es (or elasticsearch - whatever is consistent with RTGOV-342). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-388) Use jboss version of javax.servlet GAV consistently

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-388?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-388: -------------------------------- Git Pull Request: https://github.com/Governance/dtgov/pull/174, https://github.com/Governance/overlord-commons/pull/63, https://github.com/Governance/s-ramp/pull/407, https://github.com/Governance/s-ramp/commit/2f3dfcba112371f6d628471ad6f72... (was: https://github.com/Governance/dtgov/pull/174, https://github.com/Governance/overlord-commons/pull/63, https://github.com/Governance/s-ramp/pull/407) > Use jboss version of javax.servlet GAV consistently > --------------------------------------------------- > > Key: SRAMP-388 > URL: https://issues.jboss.org/browse/SRAMP-388 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Eric Wittmann > Assignee: David virgil naranjo > > EAP uses the GAV > {code} > <dependency> > <groupId>org.jboss.spec.javax.servlet</groupId> > <artifactId>jboss-servlet-api_3.0_spec</artifactId> > </dependency> > {code} > rather than > {code} > <dependency> > <groupId>javax.servlet</groupId> > <artifactId>servlet-api</artifactId> > </dependency> > {code} > This GAV is also available in the community BOM. > We need to remove all references to the javax.servlet:servlet-api dependency in all Overlord projects (s-ramp, dtgov, overlord-commons, etc). Anywhere we reference that GAV please change it to org.jboss.spec.javax.servlet:jboss-servlet-api_3.0_spec. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-411) Upgrade to Picketlink 2.5.3.SP1

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-411?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-411: -------------------------------- Git Pull Request: https://github.com/Governance/overlord-commons/pull/62, https://github.com/Governance/s-ramp/pull/406, https://github.com/Governance/overlord-commons/pull/64 (was: https://github.com/Governance/overlord-commons/pull/62, https://github.com/Governance/s-ramp/pull/406) > Upgrade to Picketlink 2.5.3.SP1 > ------------------------------- > > Key: SRAMP-411 > URL: https://issues.jboss.org/browse/SRAMP-411 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.5.0 - API Management > > > EAP 6.3 upgraded to Picketlink 2.5.3.SP1. First runs on EAP 6.3 showing breaking package changes. Ex: > java.lang.ClassNotFoundException:org.picketlink.identity.federation.core.exceptions.ConfigurationException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-382) Support EAP 6.3

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-382?page=com.atlassian.jira.plugin.... ] Eric Wittmann commented on SRAMP-382: ------------------------------------- There are no other stack traces in your log prior to that one?? > Support EAP 6.3 > --------------- > > Key: SRAMP-382 > URL: https://issues.jboss.org/browse/SRAMP-382 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 0.5.0 - API Management > > > Add support for EAP 6.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-411) Upgrade to Picketlink 2.5.3.SP1

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-411?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-411: ------------------------------ Parent: SRAMP-382 Issue Type: Sub-task (was: Task) > Upgrade to Picketlink 2.5.3.SP1 > ------------------------------- > > Key: SRAMP-411 > URL: https://issues.jboss.org/browse/SRAMP-411 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > Fix For: 0.5.0 - API Management > > > EAP 6.3 upgraded to Picketlink 2.5.3.SP1. First runs on EAP 6.3 showing breaking package changes. Ex: > java.lang.ClassNotFoundException:org.picketlink.identity.federation.core.exceptions.ConfigurationException -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues April 2014