[JBoss JIRA] (RTGOV-556) RTGov UI no longer working on FSW 6.0
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-556?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-556:
----------------------------------
Add the following properties to the end of the overlord-rtgov.properties file:
SituationStore.class=org.overlord.rtgov.analytics.situation.store.jpa.JPASituationStore
ActivityStore.class=org.overlord.rtgov.activity.store.jpa.JPAActivityStore
JPASituationStore.jndi.datasource=java:jboss/datasources/OverlordRTGov
JPAActivityStore.jndi.datasource=java:jboss/datasources/OverlordRTGov
JpaStore.jtaPlatform=org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform
# Elasticsearch configuration
Elasticsearch.hosts=embedded
Elasticsearch.schedule=30000
Elasticsearch.server=http://localhost:9700
> RTGov UI no longer working on FSW 6.0
> -------------------------------------
>
> Key: RTGOV-556
> URL: https://issues.jboss.org/browse/RTGOV-556
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
> Attachments: overlord-rtgov-elasticsearch.properties
>
>
> RTGov UI beta 1 worked on FSW 6.0, but subsequent changes to rtgov have caused it to stop working.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated SRAMP-541:
------------------------------
Git Pull Request: https://github.com/Governance/s-ramp/pull/477
> Consider removing artifact/content updates
> ------------------------------------------
>
> Key: SRAMP-541
> URL: https://issues.jboss.org/browse/SRAMP-541
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> From [~eric.wittmann] on SRAMP-539:
> {quote}
> In particular, updates are problematic with regard to derived content. What do we do with the derived artifacts if we change the content? Presumably we would delete them and re-derive. But if we do that, we might lose meta-data added to those derived artifacts manually by users. There may also be relationships that have been formed on those derived artifacts, in which case referential integrity will prevent them from being deleted, and the update will fail.
> All in all I am disappointed in myself for implementing the updateContent feature to begin with.
> {quote}
> I also agree that updateContent and artifact updates should probably be removed entirely. It's caused quite a bit of confusion, is only partially implemented, and could cause quite a bit of harm in real-world use cases.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-541:
-----------------------------------
Created the PR, but will hold off merging a bit
> Consider removing artifact/content updates
> ------------------------------------------
>
> Key: SRAMP-541
> URL: https://issues.jboss.org/browse/SRAMP-541
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> From [~eric.wittmann] on SRAMP-539:
> {quote}
> In particular, updates are problematic with regard to derived content. What do we do with the derived artifacts if we change the content? Presumably we would delete them and re-derive. But if we do that, we might lose meta-data added to those derived artifacts manually by users. There may also be relationships that have been formed on those derived artifacts, in which case referential integrity will prevent them from being deleted, and the update will fail.
> All in all I am disappointed in myself for implementing the updateContent feature to begin with.
> {quote}
> I also agree that updateContent and artifact updates should probably be removed entirely. It's caused quite a bit of confusion, is only partially implemented, and could cause quite a bit of harm in real-world use cases.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (SRAMP-541) Consider removing artifact/content updates
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-541?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-541:
-----------------------------------
Opened it up for discussion in https://community.jboss.org/message/884381
> Consider removing artifact/content updates
> ------------------------------------------
>
> Key: SRAMP-541
> URL: https://issues.jboss.org/browse/SRAMP-541
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> From [~eric.wittmann] on SRAMP-539:
> {quote}
> In particular, updates are problematic with regard to derived content. What do we do with the derived artifacts if we change the content? Presumably we would delete them and re-derive. But if we do that, we might lose meta-data added to those derived artifacts manually by users. There may also be relationships that have been formed on those derived artifacts, in which case referential integrity will prevent them from being deleted, and the update will fail.
> All in all I am disappointed in myself for implementing the updateContent feature to begin with.
> {quote}
> I also agree that updateContent and artifact updates should probably be removed entirely. It's caused quite a bit of confusion, is only partially implemented, and could cause quite a bit of harm in real-world use cases.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (OVERLORD-139) Logout not working
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/OVERLORD-139?page=com.atlassian.jira.plug... ]
Brett Meyer moved SRAMP-543 to OVERLORD-139:
--------------------------------------------
Project: Overlord (was: S-RAMP)
Key: OVERLORD-139 (was: SRAMP-543)
Affects Version/s: (was: 0.5.0.Beta3)
(was: 0.5.0.Final)
Component/s: (was: UI)
Fix Version/s: (was: 0.6.0)
> Logout not working
> ------------------
>
> Key: OVERLORD-139
> URL: https://issues.jboss.org/browse/OVERLORD-139
> Project: Overlord
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: Fedora 20
> S-RAMP installed into JBoss EAP 6.1.1.GA
> Firefox 31
> Chrome 36
> Reporter: Stefan Bunciak
> Assignee: Brett Meyer
> Priority: Blocker
>
> I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (OVERLORD-139) Logout not working
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/OVERLORD-139?page=com.atlassian.jira.plug... ]
Brett Meyer commented on OVERLORD-139:
--------------------------------------
Moved to OVERLORD -- limited to overlord-commons.
> Logout not working
> ------------------
>
> Key: OVERLORD-139
> URL: https://issues.jboss.org/browse/OVERLORD-139
> Project: Overlord
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: Fedora 20
> S-RAMP installed into JBoss EAP 6.1.1.GA
> Firefox 31
> Chrome 36
> Reporter: Stefan Bunciak
> Assignee: Brett Meyer
> Priority: Blocker
>
> I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (SRAMP-543) Logout not working
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-543?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-543:
-----------------------------------
Actually, [~eric.wittmann], this is only failing on EAP 6.1. It's working fine in 6.2/6.3 and Tomcat. Best guess: conflict between the SamlSPFilter we pulled in and the version in EAP 6.1?
> Logout not working
> ------------------
>
> Key: SRAMP-543
> URL: https://issues.jboss.org/browse/SRAMP-543
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: UI
> Affects Versions: 0.5.0.Beta3, 0.5.0.Final
> Environment: Fedora 20
> S-RAMP installed into JBoss EAP 6.1.1.GA
> Firefox 31
> Chrome 36
> Reporter: Stefan Bunciak
> Assignee: Brett Meyer
> Priority: Blocker
> Fix For: 0.6.0
>
>
> I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (SRAMP-543) Logout not working
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-543?page=com.atlassian.jira.plugin.... ]
Work on SRAMP-543 stopped by Brett Meyer.
> Logout not working
> ------------------
>
> Key: SRAMP-543
> URL: https://issues.jboss.org/browse/SRAMP-543
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: UI
> Affects Versions: 0.5.0.Beta3, 0.5.0.Final
> Environment: Fedora 20
> S-RAMP installed into JBoss EAP 6.1.1.GA
> Firefox 31
> Chrome 36
> Reporter: Stefan Bunciak
> Assignee: Brett Meyer
> Priority: Blocker
> Fix For: 0.6.0
>
>
> I logged in to S-RAMP UI, subsequently tried to logout (Click on 'admin' -> logout) and I was redirected back to s-ramp-ui, still logged in. I'm able to reproduce in both Firefox & Chrome.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months