[
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)