[JBoss JIRA] (RTGOV-452) ElasticSearch activity store impl must return full activity unit
by ivan mckinley (JIRA)
[ https://issues.jboss.org/browse/RTGOV-452?page=com.atlassian.jira.plugin.... ]
ivan mckinley commented on RTGOV-452:
-------------------------------------
Not started it.
Thanks for doing this :)
Sent from my iPad
> ElasticSearch activity store impl must return full activity unit
> ----------------------------------------------------------------
>
> Key: RTGOV-452
> URL: https://issues.jboss.org/browse/RTGOV-452
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
>
> The new Elasticsearch ActivityStore implementation decomposes the ActivityUnit into the unit and separate ActivityType objects when persisting in ElasticSearch.
> However when the implementation is returning the ActivityUnit, it only retrieves the unit part, and does not rebuild the child ActivityType objects. These also need to be retrieved to return the ActivityUnit in full.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-451) S-ramp maven facade for fuse fabric
by David virgil naranjo (JIRA)
David virgil naranjo created SRAMP-451:
------------------------------------------
Summary: S-ramp maven facade for fuse fabric
Key: SRAMP-451
URL: https://issues.jboss.org/browse/SRAMP-451
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: David virgil naranjo
Assignee: David virgil naranjo
Create a mvn-http facade component that will act as a intermediate between fuse fabric and s-ramp.. It should be just a servlet that dissects the inbound request's path to extract the GAV information. Then does a s-ramp repository query to find the appropriate artifact
The GET side of that is very easy (pulling artifacts *from* s-ramp)
The servlet would have to take a URL path like this: org/overlord/sramp/s-ramp-api/0.4.0.Final/s-ramp-api-0.4.0.Final.jar and parse that to get the GAV info of: org.overlord.sramp:s-ramp-api:0.4.0.Final:jar
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-450) S-ramp installer && S-ramp-distro add fabric as a new target
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-450?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-450:
-------------------------------------
We should prompt the user for the keystore password - I agree. Let's use the same password for both the keystore and the key. No loss of security there I don't think. The prompt should be added for all platforms I think.
The keystore should be installed by the overlord-commons installer, definitely.
And we should create the admin user (if possible) in the commons installer. If not possible/easy to create the admin user, then no user should be created at all. The s-ramp installer should never create users. However the dtgov installer should create the 'dtgovworkflows' user.
> S-ramp installer && S-ramp-distro add fabric as a new target
> ------------------------------------------------------------
>
> Key: SRAMP-450
> URL: https://issues.jboss.org/browse/SRAMP-450
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> Create a new target deployment in both the s-ramp-installer and s-ramp-distro-assembly.
> The Fabric deployment needs to unzip the overlord-commons.profile zip and the s-ramp-profile.zip inside the fabric installation.
> The question is, what to do with the keystore and the references to the keystore from the sramp-ui.properties?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-450) S-ramp installer && S-ramp-distro add fabric as a new target
by David virgil naranjo (JIRA)
[ https://issues.jboss.org/browse/SRAMP-450?page=com.atlassian.jira.plugin.... ]
David virgil naranjo commented on SRAMP-450:
--------------------------------------------
Another point about the keystore generation I think would be good to ask the user for introducing these two properties:
<entry key="s-ramp-ui.atom-api.authentication.saml.keystore-password" value="samlkeystore77" />
<entry key="s-ramp-ui.atom-api.authentication.saml.key-password" value="overlord99" />
Right now these 2 values are placed manually in the overlord-commons and in the s-ramp installer.
> S-ramp installer && S-ramp-distro add fabric as a new target
> ------------------------------------------------------------
>
> Key: SRAMP-450
> URL: https://issues.jboss.org/browse/SRAMP-450
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> Create a new target deployment in both the s-ramp-installer and s-ramp-distro-assembly.
> The Fabric deployment needs to unzip the overlord-commons.profile zip and the s-ramp-profile.zip inside the fabric installation.
> The question is, what to do with the keystore and the references to the keystore from the sramp-ui.properties?
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months