Hello ARSLIST, If anyone has successfully integrated Remedy Midtier (7.6.4) with SiteMinder SSO, we really need to speak with you. Though we have it working in instances where the SSO Login Name matches the Remedy User Login Name, we cannot for the life of us get it to work where the Login Names differ and SSO is passing us an alias. Below is more detailed information on it:
We are leveraging an unsupported Midter_AREA_SSO integration. The objective is to login to the SiteMinder login page (which resides on the Remedy midtier) using your single-sign on; and then once validated in SiteMinder with your single sign-on password; Siteminder sends Remedy back the Remedy login name in a header. Within Remedy, our login names differ from the standard single sign-on used at our company. I am able to successfully connect to SiteMinder for login; but it doesnt appear that midtier or IIS is accepting the header that SiteMinder is passing back which includes the alias (aka Remdy login name). I'm not sure if anyone out there has tried to integrate to SiteMinder using this method of having SiteMinder send back an alias in a header for Remedy login (the remedy login name) upon successful validation to SiteMinder using standard/global Single Sign-on password. I do not see the header being passed or even header name value in the Fiddler logs. The main problem appears to be that the Midtier or IIS is not accepting the header that SiteMinder is passing back which includes the alias (the Remedy Login Name). If anyone can offer any insight into this issue, we would greatly appreciate it! Thank you so much! ARS 7.6.4 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
