[JBoss JIRA] (SRAMP-440) Add a final redirect filter to overlord SPs
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-440?page=com.atlassian.jira.plugin.... ]
Brett Meyer reopened SRAMP-440:
-------------------------------
> Add a final redirect filter to overlord SPs
> -------------------------------------------
>
> Key: SRAMP-440
> URL: https://issues.jboss.org/browse/SRAMP-440
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: UI
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 0.5.0
>
>
> The IDP (when running in tomcat, jetty, fuse) causes the browser to do a POST of the SAML assertion to the SP (e.g. s-ramp-ui). This POST is consumed by the SPFilter and the assertion is consumed. At this point the user is authenticated and the UI is loaded.
> However, if the user then tries to refresh the page, the browser will likely ask if the user wishes to Resend data.
> To avoid this problem we should have a filter that does a final redirect (only after a POST to the SPFilter) so that the browser finishes up with a GET request to the UI rather than a POST.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (SRAMP-528) Include fuse fabric installer for sramp and dtgov
by David virgil naranjo (JIRA)
David virgil naranjo created SRAMP-528:
------------------------------------------
Summary: Include fuse fabric installer for sramp and dtgov
Key: SRAMP-528
URL: https://issues.jboss.org/browse/SRAMP-528
Project: S-RAMP
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: David virgil naranjo
Assignee: David virgil naranjo
Include a new entry in the sramp-distro and dtgov-distro assembly projects.
It will generate the profiles to be deployed in fuse fabric. It will ask the user for the keystore password and generate the overlord-saml.keystore
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
[JBoss JIRA] (SRAMP-508) Restrict s-ramp artifacts depends on the environment
by David virgil naranjo (JIRA)
[ https://issues.jboss.org/browse/SRAMP-508?page=com.atlassian.jira.plugin.... ]
David virgil naranjo updated SRAMP-508:
---------------------------------------
Git Pull Request: https://github.com/Governance/s-ramp/pull/464
> Restrict s-ramp artifacts depends on the environment
> -----------------------------------------------------
>
> Key: SRAMP-508
> URL: https://issues.jboss.org/browse/SRAMP-508
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: David virgil naranjo
> Assignee: David virgil naranjo
>
> By default the S-RAMP Maven integration should not allow maven snapshots to be deployed to the s-ramp repository (since this is not a use-case we want to encourage). However, we are planning to support maven snapshots in the code via a flag to enable/disable the support. This flag will be consumed by the maven repository facade. The flag (e.g. s-ramp.maven.enable-snapshots) will default to *false* unless the S-RAMP runtime itself is a SNAPSHOT.
> This will make it easier for us during development of s-ramp and dtgov to test out our demos and dtgov seed data without changing the versions of those artifacts in their respective pom.xml files.
> So in summary - the maven repo facade will not allow SNAPSHOT artifacts to be deployed unless the flag is set to true *or* the current s-ramp runtime version is a snapshot version.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months