[JBoss JIRA] (SRAMP-197) Auditing: re-implement *not* using JCR observer pattern
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-197:
-----------------------------------
Summary: Auditing: re-implement *not* using JCR observer pattern
Key: SRAMP-197
URL: https://issues.jboss.org/browse/SRAMP-197
Project: S-RAMP
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Core
Affects Versions: 0.2.0 - Security & S-RAMP-1.0
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: 0.3.0 - JBPM6 Integration
Re-write the core auditing to no longer use the JCR observer pattern. The JCR observer pattern introduces a number of challenges, including:
1) async processing of auditing information. this is problematic in a number of ways, but most importantly is that data may be lost due to slower processing of the auditing information than the information on the artifact itself. Since the JCR observation events don't contain before and/or after values for changes, we have to go after the data directly. If changes happen quickly (before the observer has a crack at it) then data may be lost.
2) multi-phase processing of artifact adds/updates in the jcrpersistence impl
--
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
11 years, 7 months
[JBoss JIRA] (SRAMP-196) Add the contentHash property for Document style artifacts
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-196:
-----------------------------------
Summary: Add the contentHash property for Document style artifacts
Key: SRAMP-196
URL: https://issues.jboss.org/browse/SRAMP-196
Project: S-RAMP
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Core, Persistence
Reporter: Eric Wittmann
Assignee: Kurt Stam
Fix For: 0.3.0 - JBPM6 Integration
The persistence manager should create a SHA-1 hash for every document style artifact. The CND already has the contentHash property defined, but the persistence manager doesn't calculate and store it yet.
Note: the contentHash also is not being returned (needs to be added to the JCRNodeToArtifactVisitor in visitDocument.
Unit tests for this should not use TextDocument (to avoid windows/unix line ending differences in git).
--
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
11 years, 7 months
[JBoss JIRA] (RTGOV-159) Apply RTGov branding to gadget server when installing
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/RTGOV-159?page=com.atlassian.jira.plugin.... ]
Eric Wittmann resolved RTGOV-159.
---------------------------------
Resolution: Done
Now using the Overlord UI header from overlord-commons-uiheader. I had to slightly modify the gadget UI to make room for the Overlord header. The gadget UI uses all absolute positioning, so there is some GWT code that pushes everything down enough for the UI to be visible without obscuring anything else.
> Apply RTGov branding to gadget server when installing
> -----------------------------------------------------
>
> Key: RTGOV-159
> URL: https://issues.jboss.org/browse/RTGOV-159
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Reporter: Gary Brown
> Assignee: Eric Wittmann
> Fix For: 1.0.0.Final
>
>
> When installing the gadget server as part of an RTGov installation, replace the branding with a RTGov specific one.
> The branding should be consistent with the one used by DTGov.
--
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
11 years, 7 months
[JBoss JIRA] (RTGOV-59) Enable security on REST services
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/RTGOV-59?page=com.atlassian.jira.plugin.s... ]
Eric Wittmann resolved RTGOV-59.
--------------------------------
Resolution: Done
I implemented this by doing the following:
1) merged gadget-server and gadget-web into the same web application context - this allows the browser to easily make rpc/ajax calls to either the shindig server (for gadget.io.makeRequest calls) or the GWT endpoints regardless of the type of authentication being used
2) all gadget-web services are now in the same guice injection context as shindig, allowing gadget-web GWT services to use shindig services directly
3) implemented a custom shindig http fetcher that supports Overlord SAML based authentication of outgoing REST calls
> Enable security on REST services
> --------------------------------
>
> Key: RTGOV-59
> URL: https://issues.jboss.org/browse/RTGOV-59
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Reporter: Gary Brown
> Assignee: Eric Wittmann
> Priority: Critical
> Fix For: 1.0.0.Final
>
>
--
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
11 years, 7 months