[ https://issues.jboss.org/browse/SRAMPUI-94?page=com.atlassian.jira.plugin... ]
Eric Wittmann resolved SRAMPUI-94.
----------------------------------
Resolution: Done
> Login Page: "JBoss Overlord" font should be bold
> ------------------------------------------------
>
> Key: SRAMPUI-94
> URL: https://issues.jboss.org/browse/SRAMPUI-94
> Project: S-RAMP UI
> Issue Type: Enhancement
> Components: View
> Affects Versions: 0.3.0
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.1
>
>
> The JBoss Overlord text should have:
> font-weight: bold
--
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
[ https://issues.jboss.org/browse/SRAMPUI-94?page=com.atlassian.jira.plugin... ]
Eric Wittmann closed SRAMPUI-94.
--------------------------------
> Login Page: "JBoss Overlord" font should be bold
> ------------------------------------------------
>
> Key: SRAMPUI-94
> URL: https://issues.jboss.org/browse/SRAMPUI-94
> Project: S-RAMP UI
> Issue Type: Enhancement
> Components: View
> Affects Versions: 0.3.0
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.1
>
>
> The JBoss Overlord text should have:
> font-weight: bold
--
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
[ https://issues.jboss.org/browse/SRAMPUI-94?page=com.atlassian.jira.plugin... ]
Work on SRAMPUI-94 started by Eric Wittmann.
> Login Page: "JBoss Overlord" font should be bold
> ------------------------------------------------
>
> Key: SRAMPUI-94
> URL: https://issues.jboss.org/browse/SRAMPUI-94
> Project: S-RAMP UI
> Issue Type: Enhancement
> Components: View
> Affects Versions: 0.3.0
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.1
>
>
> The JBoss Overlord text should have:
> font-weight: bold
--
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
[ https://issues.jboss.org/browse/SRAMP-237?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-237:
--------------------------------
Git Pull Request: https://github.com/Governance/s-ramp/pull/315
> Demo (s-ramp-demos-switchyard) not properly deploying
> -----------------------------------------------------
>
> Key: SRAMP-237
> URL: https://issues.jboss.org/browse/SRAMP-237
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 0.3.0 - JBPM6 Integration
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> The s-ramp-demos-switchyard demo is not working because it's missing some markup in the demo profile to re-enable deployments. Deployments are being skipped (presumably due to a setting in a parent pom) and need to be explicitly un-skipped in the demo pom.
--
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
[ https://issues.jboss.org/browse/SRAMP-237?page=com.atlassian.jira.plugin.... ]
Eric Wittmann resolved SRAMP-237.
---------------------------------
Resolution: Done
> Demo (s-ramp-demos-switchyard) not properly deploying
> -----------------------------------------------------
>
> Key: SRAMP-237
> URL: https://issues.jboss.org/browse/SRAMP-237
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 0.3.0 - JBPM6 Integration
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> The s-ramp-demos-switchyard demo is not working because it's missing some markup in the demo profile to re-enable deployments. Deployments are being skipped (presumably due to a setting in a parent pom) and need to be explicitly un-skipped in the demo pom.
--
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
[ https://issues.jboss.org/browse/SRAMP-237?page=com.atlassian.jira.plugin.... ]
Eric Wittmann closed SRAMP-237.
-------------------------------
> Demo (s-ramp-demos-switchyard) not properly deploying
> -----------------------------------------------------
>
> Key: SRAMP-237
> URL: https://issues.jboss.org/browse/SRAMP-237
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 0.3.0 - JBPM6 Integration
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> The s-ramp-demos-switchyard demo is not working because it's missing some markup in the demo profile to re-enable deployments. Deployments are being skipped (presumably due to a setting in a parent pom) and need to be explicitly un-skipped in the demo pom.
--
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
[ https://issues.jboss.org/browse/SRAMP-237?page=com.atlassian.jira.plugin.... ]
Work on SRAMP-237 started by Eric Wittmann.
> Demo (s-ramp-demos-switchyard) not properly deploying
> -----------------------------------------------------
>
> Key: SRAMP-237
> URL: https://issues.jboss.org/browse/SRAMP-237
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 0.3.0 - JBPM6 Integration
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.3.1 - jBPM - bugfix 1
>
>
> The s-ramp-demos-switchyard demo is not working because it's missing some markup in the demo profile to re-enable deployments. Deployments are being skipped (presumably due to a setting in a parent pom) and need to be explicitly un-skipped in the demo pom.
--
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
[ https://issues.jboss.org/browse/RTGOV-270?page=com.atlassian.jira.plugin.... ]
Eric Wittmann closed RTGOV-270.
-------------------------------
> Need SAML bearer token support in gadget-server/rtgov
> -----------------------------------------------------
>
> Key: RTGOV-270
> URL: https://issues.jboss.org/browse/RTGOV-270
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Components: Gadgets
> Affects Versions: 1.0.0.Final
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 2.0.0.M1
>
>
> Currently we use BASIC auth when communicating between the gadget server servlet layer and the rtgov REST services. This should be changed to use saml bearer token auth instead (which will allow us to remove the credentials from the gadget-server config file).
--
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
[ https://issues.jboss.org/browse/RTGOV-270?page=com.atlassian.jira.plugin.... ]
Eric Wittmann resolved RTGOV-270.
---------------------------------
Resolution: Done
> Need SAML bearer token support in gadget-server/rtgov
> -----------------------------------------------------
>
> Key: RTGOV-270
> URL: https://issues.jboss.org/browse/RTGOV-270
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Components: Gadgets
> Affects Versions: 1.0.0.Final
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 2.0.0.M1
>
>
> Currently we use BASIC auth when communicating between the gadget server servlet layer and the rtgov REST services. This should be changed to use saml bearer token auth instead (which will allow us to remove the credentials from the gadget-server config file).
--
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