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