[
https://issues.jboss.org/browse/SRAMP-445?page=com.atlassian.jira.plugin....
]
Brett Meyer commented on SRAMP-445:
-----------------------------------
+1, especially if reverting would be fairly invasive. Outside of possibly Fuse/EAP, SSO
seems like a "really nice to have", but definitely not a blocker.
Would creating a Tomcat issue, providing some context, and simply attaching an
overlord-idp.war suffice? I'm wondering if creating a from-scratch standalone test
would be worth the effort, depending on what they actually need to debug...
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.6.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)