Make sure you have the SSOAuthenticator in config.properties file instead
of the deafultAuthenticator.
HTH
On Fri, Jun 28, 2013 at 10:37 AM, Howard C hcm...@yahoo.com wrote:
7.6.4
___
UNSUBSCRIBE or access ARSlist
Hello,
Using HTTP headers isn't a great solution. If you're integrating with
SiteMinder, you need to process the SiteMinder cookie to check the user
is both authenticated, and authorised, to access the application (ie
ITSM) which OpenSSO (and hence AtriumSSO) does not do. OpenSSO (and
hence
7.6.4
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years
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
What cersion of ARS do you have.
-Original Message-
From: Howard C hcm...@yahoo.com
To: arslist arslist@ARSLIST.ORG
Sent: Thu, Jun 27, 2013 5:20 pm
Subject: Siteminder SSO Mid-Tier Question
We currently have Siteminder SSO integrated with our Mid-Tier. Siteminder s
assing the header
-Tier Question
** What cersion of ARS do you have.
-Original Message-
From: Howard C hcm...@yahoo.com
To: arslist arslist@ARSLIST.ORG
Sent: Thu, Jun 27, 2013 5:20 pm
Subject: Siteminder SSO Mid-Tier Question
We currently have Siteminder SSO integrated with our Mid-Tier. Siteminder s
6 matches
Mail list logo