[JBoss JIRA] (RTGOV-478) NPE when retrieving situation list from rtgov-ui in FSW 6.0
by Michael Clay (JIRA)
[ https://issues.jboss.org/browse/RTGOV-478?page=com.atlassian.jira.plugin.... ]
Michael Clay commented on RTGOV-478:
------------------------------------
the NPE is caused from a call to the RTGovSituationsProvider#search because SituationStore _situationStore is null
-> the reason is SituationStoreFactory#getSituationStore can't find a SITUATION_STORE_CLASS property in the configured ./standalone/configuration/overlord-rtgov.properties
> NPE when retrieving situation list from rtgov-ui in FSW 6.0
> -----------------------------------------------------------
>
> Key: RTGOV-478
> URL: https://issues.jboss.org/browse/RTGOV-478
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Interface
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
>
> When deploying the rtgov-ui to FSW 6.0 (war found in the ui/overlord-rtgov-ui-war-fsw60 module, accessing the situations page shows a null pointer exception in a popup window.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (SRAMP-445) SSO not working on Tomcat
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-445?page=com.atlassian.jira.plugin.... ]
Work on SRAMP-445 started by Eric Wittmann.
> SSO not working on Tomcat
> -------------------------
>
> Key: SRAMP-445
> URL: https://issues.jboss.org/browse/SRAMP-445
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.5.0.Final
>
>
> The IDP isn't quite working as an SSO provider when running in Tomcat. The SP properly redirects to the IDP but the IDP is requiring the user to authenticate again, even though they already have. To reproduce:
> 1) run both s-ramp and dtgov on tomcat
> 2) open browser, navigate to s-ramp-ui
> 3) log in
> 4) click on Design Time Governance
> At this point you will have to authenticate again. This is wrong.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (SRAMP-445) SSO not working on Tomcat
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-445?page=com.atlassian.jira.plugin.... ]
Eric Wittmann reassigned SRAMP-445:
-----------------------------------
Assignee: Eric Wittmann (was: Brett Meyer)
> SSO not working on Tomcat
> -------------------------
>
> Key: SRAMP-445
> URL: https://issues.jboss.org/browse/SRAMP-445
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.5.0.Final
>
>
> The IDP isn't quite working as an SSO provider when running in Tomcat. The SP properly redirects to the IDP but the IDP is requiring the user to authenticate again, even though they already have. To reproduce:
> 1) run both s-ramp and dtgov on tomcat
> 2) open browser, navigate to s-ramp-ui
> 3) log in
> 4) click on Design Time Governance
> At this point you will have to authenticate again. This is wrong.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (SRAMP-451) S-ramp maven facade for fuse fabric
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-451?page=com.atlassian.jira.plugin.... ]
Eric Wittmann closed SRAMP-451.
-------------------------------
> 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
> Fix For: 0.5.0.Final
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> 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.6#6264)
10 years
[JBoss JIRA] (SRAMP-451) S-ramp maven facade for fuse fabric
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-451?page=com.atlassian.jira.plugin.... ]
Eric Wittmann resolved SRAMP-451.
---------------------------------
Resolution: Done
> 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
> Fix For: 0.5.0.Final
>
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> 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.6#6264)
10 years
[JBoss JIRA] (SRAMP-470) Maven Facade: Improve authentication
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-470?page=com.atlassian.jira.plugin.... ]
Eric Wittmann updated SRAMP-470:
--------------------------------
Git Pull Request: https://github.com/Governance/s-ramp/pull/443
> Maven Facade: Improve authentication
> ------------------------------------
>
> Key: SRAMP-470
> URL: https://issues.jboss.org/browse/SRAMP-470
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: S-RAMP API
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.5.0.Final
>
>
> Currently the maven facade requires authentication because we do not have a mechanism for providing selective read-only access to the JCR repository. However, the Maven Facade should be a read-only (for Maven GET operations) window into the s-ramp data.
> We need to do two things:
> 1) If the Maven Facade Request has authentication credentials associated with it, use them to log into the s-ramp repository
> 2) If the Maven Facade Request does *not* have authentication credentials associated with it, then log into JCR using read-only credentials
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (SRAMP-470) Maven Facade: Improve authentication
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-470?page=com.atlassian.jira.plugin.... ]
Eric Wittmann resolved SRAMP-470.
---------------------------------
Resolution: Done
> Maven Facade: Improve authentication
> ------------------------------------
>
> Key: SRAMP-470
> URL: https://issues.jboss.org/browse/SRAMP-470
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: S-RAMP API
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.5.0.Final
>
>
> Currently the maven facade requires authentication because we do not have a mechanism for providing selective read-only access to the JCR repository. However, the Maven Facade should be a read-only (for Maven GET operations) window into the s-ramp data.
> We need to do two things:
> 1) If the Maven Facade Request has authentication credentials associated with it, use them to log into the s-ramp repository
> 2) If the Maven Facade Request does *not* have authentication credentials associated with it, then log into JCR using read-only credentials
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years
[JBoss JIRA] (SRAMP-470) Maven Facade: Improve authentication
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-470?page=com.atlassian.jira.plugin.... ]
Eric Wittmann closed SRAMP-470.
-------------------------------
> Maven Facade: Improve authentication
> ------------------------------------
>
> Key: SRAMP-470
> URL: https://issues.jboss.org/browse/SRAMP-470
> Project: S-RAMP
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: S-RAMP API
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.5.0.Final
>
>
> Currently the maven facade requires authentication because we do not have a mechanism for providing selective read-only access to the JCR repository. However, the Maven Facade should be a read-only (for Maven GET operations) window into the s-ramp data.
> We need to do two things:
> 1) If the Maven Facade Request has authentication credentials associated with it, use them to log into the s-ramp repository
> 2) If the Maven Facade Request does *not* have authentication credentials associated with it, then log into JCR using read-only credentials
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years