May 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-435) Investigate porting S-RAMP CLI to Felix commands

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-435?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-435: ------------------------------ Summary: Investigate porting S-RAMP CLI to Felix commands (was: Investigate porting S-RAMP CLI to Karaf commands) > Investigate porting S-RAMP CLI to Felix commands > ------------------------------------------------ > > Key: SRAMP-435 > URL: https://issues.jboss.org/browse/SRAMP-435 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: Brett Meyer > > It could be really useful to allow our CLI to be used within the Fuse console. Attempt to port them to Karaf commands. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-458) ActivityServer integration test using deprecated query method

by Gary Brown (JIRA)

Gary Brown created RTGOV-458: -------------------------------- Summary: ActivityServer integration test using deprecated query method Key: RTGOV-458 URL: https://issues.jboss.org/browse/RTGOV-458 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final The JBossASActivityServerServiceTest tested the activity server query method via the REST API. The issue was it relied on the JPA query language - hence this method was deprecated as it exposed the implementation. Need to add further tests for the getActivityTypes and getActivityUnit method, to replace the query methods. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-429) Move jetty login-realm config from s-ramp installer to overlord-commons installer

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-429?page=com.atlassian.jira.plugin.... ] Eric Wittmann commented on SRAMP-429: ------------------------------------- The realm should also be configured when running in Fuse (not just Jetty). It's the same change - modify the jetty.xml to add the new realm. Note: it might be slightly different markup in Fuse than in Jetty. > Move jetty login-realm config from s-ramp installer to overlord-commons installer > --------------------------------------------------------------------------------- > > Key: SRAMP-429 > URL: https://issues.jboss.org/browse/SRAMP-429 > Project: S-RAMP > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Distro > Affects Versions: 0.4.0 - Tomcat Support > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0 - API Management > > > Currently we simply replace the jetty.xml in the s-ramp installer for jetty8. Instead we should transform the existing one to add what we want. The s-ramp installer should add the s-ramp datasource. The overlord-commons installer should add the idp realm. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-437) Getting a 404 on the first attempt to access s-ramp-ui when in Fuse 6.1

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-437?page=com.atlassian.jira.plugin.... ] Eric Wittmann updated SRAMP-437: -------------------------------- Description: After the first time it works ok. Probably has something to do with the ;jessionid= that is getting dumped onto the end of the URL. > Getting a 404 on the first attempt to access s-ramp-ui when in Fuse 6.1 > ----------------------------------------------------------------------- > > Key: SRAMP-437 > URL: https://issues.jboss.org/browse/SRAMP-437 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: UI > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.5.0 - API Management > > > After the first time it works ok. Probably has something to do with the ;jessionid= that is getting dumped onto the end of the URL. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-437) Getting a 404 on the first attempt to access s-ramp-ui when in Fuse 6.1

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-437: ----------------------------------- Summary: Getting a 404 on the first attempt to access s-ramp-ui when in Fuse 6.1 Key: SRAMP-437 URL: https://issues.jboss.org/browse/SRAMP-437 Project: S-RAMP Issue Type: Bug Security Level: Public (Everyone can see) Components: UI Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: 0.5.0 - API Management -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 4 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 commented on SRAMP-436: ------------------------------------- Note: the saml bearer token auth technique *is* signing the assertions by default. But the SSO doesn't sign its assertion prior to returning it to the SP. And the SP doesn't check for a sig. Both of these need to be fixed. I anticipate that a resulting challenge will be how to configure the path to the keystore. Perhaps we can have custom versions of the servlet filters which can do platform-specific searching for it. > 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 - API Management > > > Currently we're not signing the saml assertions. We need to do that. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 4 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: -------------------------------- Fix Version/s: 0.5.0 - API Management > 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 - API Management > > > Currently we're not signing the saml assertions. We need to do that. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 4 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)

Eric Wittmann created SRAMP-436: ----------------------------------- Summary: 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 Currently we're not signing the saml assertions. We need to do that. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-435) Investigate porting S-RAMP CLI to Karaf commands

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-435: --------------------------------- Summary: Investigate porting S-RAMP CLI to Karaf commands Key: SRAMP-435 URL: https://issues.jboss.org/browse/SRAMP-435 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer It could be really useful to allow our CLI to be used within the Fuse console. Attempt to port them to Karaf commands. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-457) Situation json now includes 'properties' and 'situationProperties'

by Gary Brown (JIRA)

Gary Brown created RTGOV-457: -------------------------------- Summary: Situation json now includes 'properties' and 'situationProperties' Key: RTGOV-457 URL: https://issues.jboss.org/browse/RTGOV-457 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Gary Brown Assignee: Gary Brown Fix For: 2.0.0.Final In the recent move from JPA to Hibernate ORM it was found that queries could not work on properties, as 'properties' is a hibernate keyword - so the situationProperties property was added and the old properties getter/setter deprecated, to maintain programmatic backward compatibility. The db schema is ok as the column name is the same. Moving forward it is probably better that the json reflects the object properties, so should use 'situationProperties' - so need to mark 'properties' as transient so not converted to json. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues May 2014