We currently have Siteminder SSO integrated with our Mid-Tier.  Siteminder is 
passing the header name over to Remedy but I don't believe Remedy is consuming 
it.  After signing into SSO the Remedy native logon page appears instead of 
being logged into the system.  The config.properties file contains the path to 
the sso.properties file and the header name is designated in the sso.properties 
file.  What other configuration is needed to get it to work?
 
Any help will be greatly appreciated.

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to