December 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() should be persisted and queryable

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-622?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-622: ----------------------------------- These also need to be queryable. Suggestion: /s-ramp/wsdl/WsdlDocument[includedXsds[s-ramp:getRelationshipAttribute(., 'someAttribute') = 'true]] > Relationship.getOtherAttributes() should be persisted and queryable > ------------------------------------------------------------------- > > Key: SRAMP-622 > URL: https://issues.jboss.org/browse/SRAMP-622 > Project: S-RAMP > Issue Type: Bug > Components: Persistence > Affects Versions: 0.7.0.Final > Reporter: Lukas Krejci > Assignee: Brett Meyer > Attachments: reproducer.zip > > > The API allows for the relationships to have arbitrary "other" attributes on them. > These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (SRAMP-622) Relationship.getOtherAttributes() should be persisted and queryable

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-622?page=com.atlassian.jira.plugin.... ] Brett Meyer updated SRAMP-622: ------------------------------ Summary: Relationship.getOtherAttributes() should be persisted and queryable (was: Relationship.getOtherAttributes() not persisted) > Relationship.getOtherAttributes() should be persisted and queryable > ------------------------------------------------------------------- > > Key: SRAMP-622 > URL: https://issues.jboss.org/browse/SRAMP-622 > Project: S-RAMP > Issue Type: Bug > Components: Persistence > Affects Versions: 0.7.0.Final > Reporter: Lukas Krejci > Assignee: Brett Meyer > Attachments: reproducer.zip > > > The API allows for the relationships to have arbitrary "other" attributes on them. > These attributes don't seem to be persisted. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-627) Separate out governance from rtgov config for KeyCloak

by Gary Brown (JIRA)

Gary Brown created RTGOV-627: -------------------------------- Summary: Separate out governance from rtgov config for KeyCloak Key: RTGOV-627 URL: https://issues.jboss.org/browse/RTGOV-627 Project: RTGov (Run Time Governance) Issue Type: Task Reporter: Gary Brown Assignee: Gary Brown Currently there are two XSLT transformations, one used when there is no keycloak installed, and the other to create the config for the governance and rtgov specific details. To enable rtgov to be installed where keycloak and the governance realm have already been installed, we should separate out the governance realm creation. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-595) List of services can't be refreshed on EAP/Fuse

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-595?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-595. ------------------------------ Resolution: Done > List of services can't be refreshed on EAP/Fuse > ----------------------------------------------- > > Key: RTGOV-595 > URL: https://issues.jboss.org/browse/RTGOV-595 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: EAP 6.3 + switchyard 2.0.0.Alpha2 + rtgov 2.0.0.Final > Reporter: Andrej Vano > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > If you access the services page, the deployed services are immediately listed correctly. When you hit the refresh button, the list of services can't be refreshed - it will hang on Finding services, please wait... (no result even after 2 mins) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-595) List of services can't be refreshed on EAP/Fuse

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-595?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-595: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/243 > List of services can't be refreshed on EAP/Fuse > ----------------------------------------------- > > Key: RTGOV-595 > URL: https://issues.jboss.org/browse/RTGOV-595 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Components: User Interface > Affects Versions: 2.0.0.Final > Environment: EAP 6.3 + switchyard 2.0.0.Alpha2 + rtgov 2.0.0.Final > Reporter: Andrej Vano > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > If you access the services page, the deployed services are immediately listed correctly. When you hit the refresh button, the list of services can't be refreshed - it will hang on Finding services, please wait... (no result even after 2 mins) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-620) Support basic auth for REST services using users configured in KeyCloak

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-620?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-620. ------------------------------ Resolution: Done > Support basic auth for REST services using users configured in KeyCloak > ----------------------------------------------------------------------- > > Key: RTGOV-620 > URL: https://issues.jboss.org/browse/RTGOV-620 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > KeyCloak SSO support is being added in RTGOV-609. However it is currently not possible to have a REST service both support KeyCloak bearer tokens and basic auth (using KeyCloak's configured users). > Need to find way to support basic auth for REST services to maintain backward compatible usage. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

[JBoss JIRA] (RTGOV-620) Support basic auth for REST services using users configured in KeyCloak

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-620?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-620: ----------------------------- Git Pull Request: https://github.com/Governance/rtgov/pull/242 > Support basic auth for REST services using users configured in KeyCloak > ----------------------------------------------------------------------- > > Key: RTGOV-620 > URL: https://issues.jboss.org/browse/RTGOV-620 > Project: RTGov (Run Time Governance) > Issue Type: Task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.1.0.Final > > > KeyCloak SSO support is being added in RTGOV-609. However it is currently not possible to have a REST service both support KeyCloak bearer tokens and basic auth (using KeyCloak's configured users). > Need to find way to support basic auth for REST services to maintain backward compatible usage. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues December 2014