[JBoss JIRA] (SRAMP-445) SSO not working on Tomcat
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/SRAMP-445?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on SRAMP-445:
----------------------------------
My vote is to leave as is - it is inconvenient to log into the separate project UIs, but not a show stopper, especially when a lot of users may only be using a single project.
> 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
>
>
> 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)
12 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 commented on SRAMP-445:
-------------------------------------
Yeah it's on my to-do list to create a standalone reproducer and then log a bug for tomcat. I don't know how hard that will be.
However, to be clear the impact of this is that the user has to authenticate separately for each project (s-ramp, dtgov, rtgov). It does not *prevent* authentication at the moment. It may also mean that users will need to re-authenticate when their (e.g.) s-ramp UI session expires. These sessions don't expire easily, however, due to errai chattiness.
For this reason I think we can defer this.
However, if we think this is critical for the next Overlord release then I suggest we revert the IDP and SPs to their Tomcat Valve-specific implementations. This requires changes to the various WARs as well as the installer (as mentioned earlier).
> 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
>
>
> 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)
12 years
[JBoss JIRA] (RTGOV-523) Situation Call trace UI shows traces for all situations in system
by ivan mckinley (JIRA)
[ https://issues.jboss.org/browse/RTGOV-523?page=com.atlassian.jira.plugin.... ]
ivan mckinley updated RTGOV-523:
--------------------------------
Attachment: calltrace.png
> Situation Call trace UI shows traces for all situations in system
> ------------------------------------------------------------------
>
> Key: RTGOV-523
> URL: https://issues.jboss.org/browse/RTGOV-523
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Interface
> Affects Versions: 2.0.0.Final
> Reporter: ivan mckinley
> Assignee: Gary Brown
> Attachments: calltrace.png
>
>
> See screenshot.
> Reproduce
> - build and deploy ordermanagement example
> - build and deploy SLA example
> -in the order managemen app/ folder run the order3 which generates SLA situations
> mvn exec:java -Dreq=order3 -Dcount=10
> Naviate to the situation UI and select any of the 10 SLAs show. the call trace of the selected situation shows call traces of other situations
> see screen shot
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
12 years
[JBoss JIRA] (RTGOV-523) Situation Call trace UI shows traces for all situations in system
by ivan mckinley (JIRA)
[ https://issues.jboss.org/browse/RTGOV-523?page=com.atlassian.jira.plugin.... ]
ivan mckinley updated RTGOV-523:
--------------------------------
Attachment: (was: screenshot-1.png)
> Situation Call trace UI shows traces for all situations in system
> ------------------------------------------------------------------
>
> Key: RTGOV-523
> URL: https://issues.jboss.org/browse/RTGOV-523
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Interface
> Affects Versions: 2.0.0.Final
> Reporter: ivan mckinley
> Assignee: Gary Brown
>
> See screenshot.
> Reproduce
> - build and deploy ordermanagement example
> - build and deploy SLA example
> -in the order managemen app/ folder run the order3 which generates SLA situations
> mvn exec:java -Dreq=order3 -Dcount=10
> Naviate to the situation UI and select any of the 10 SLAs show. the call trace of the selected situation shows call traces of other situations
> see screen shot
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
12 years
[JBoss JIRA] (RTGOV-523) Situation Call trace UI shows traces for all situations in system
by ivan mckinley (JIRA)
[ https://issues.jboss.org/browse/RTGOV-523?page=com.atlassian.jira.plugin.... ]
ivan mckinley updated RTGOV-523:
--------------------------------
Attachment: screenshot-1.png
> Situation Call trace UI shows traces for all situations in system
> ------------------------------------------------------------------
>
> Key: RTGOV-523
> URL: https://issues.jboss.org/browse/RTGOV-523
> Project: RTGov (Run Time Governance)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Interface
> Affects Versions: 2.0.0.Final
> Reporter: ivan mckinley
> Assignee: Gary Brown
>
> See screenshot.
> Reproduce
> - build and deploy ordermanagement example
> - build and deploy SLA example
> -in the order managemen app/ folder run the order3 which generates SLA situations
> mvn exec:java -Dreq=order3 -Dcount=10
> Naviate to the situation UI and select any of the 10 SLAs show. the call trace of the selected situation shows call traces of other situations
> see screen shot
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
12 years
[JBoss JIRA] (RTGOV-523) Situation Call trace UI shows traces for all situations in system
by ivan mckinley (JIRA)
ivan mckinley created RTGOV-523:
-----------------------------------
Summary: Situation Call trace UI shows traces for all situations in system
Key: RTGOV-523
URL: https://issues.jboss.org/browse/RTGOV-523
Project: RTGov (Run Time Governance)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: User Interface
Affects Versions: 2.0.0.Final
Reporter: ivan mckinley
Assignee: Gary Brown
See screenshot.
Reproduce
- build and deploy ordermanagement example
- build and deploy SLA example
-in the order managemen app/ folder run the order3 which generates SLA situations
mvn exec:java -Dreq=order3 -Dcount=10
Naviate to the situation UI and select any of the 10 SLAs show. the call trace of the selected situation shows call traces of other situations
see screen shot
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
12 years
[JBoss JIRA] (SRAMP-445) SSO not working on Tomcat
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/SRAMP-445?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on SRAMP-445:
----------------------------------
Would it be worth logging the bug with a simple test case on the tomcat jira to see whether there are any suggestions?
Although it is unlikely to get fixed quickly - so are there any other interim solutions, even if not so user friendly? like going back to form authentication per project?
> 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
>
>
> 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)
12 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 stopped 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
>
>
> 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)
12 years