Re: Remedy 7.6 Midtier Integration with SiteMinder SSO

2015-01-09 Thread Rick Cook
Carol, have you considered using the authentication alias field on the User
Form?  I wonder if that might help.

Rick
On Jan 9, 2015 12:38 PM, Carol Carnevali carol.carnev...@broadridge.com
wrote:

 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


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


Remedy 7.6 Midtier Integration with SiteMinder SSO

2015-01-09 Thread Carol Carnevali
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


Re: Remedy 7.6 Midtier Integration with SiteMinder SSO

2015-01-09 Thread Carol Carnevali
Wow, Rick, could it be as simple as that?  We will definitely give that a try!

Thank you so much!

Carol

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


Re: Knowledgebase design in SNow is almost the exact design as the Knowledgebase in Remedy...

2015-01-09 Thread Pierson, Shawn
Aren’t Hyundai the more reliable car of the two?

Thanks,

Shawn Pierson
Remedy Developer | Energy Transfer

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Saji Philip
Sent: Thursday, January 08, 2015 7:45 PM
To: arslist@ARSLIST.ORG
Subject: Re: Knowledgebase design in SNow is almost the exact design as the 
Knowledgebase in Remedy...

**

They say best form of flattery is to imitation..  But I would like to drive a 
Jaguar more so then a Hyundai...
On Jan 8, 2015 7:13 PM, Joe D'Souza 
jdso...@shyle.netmailto:jdso...@shyle.net wrote:
**
Absolutely not! The first time I saw a Hyundai Sonata’s 2000 model (I think) I 
thought it was a complete rip off of the Jaguar including the way the car was 
dressed with its trims and lights etc.

I saw another that was a rip off of the BMW 5 series – I do not recall which 
one that was.

One could understand a motorcycle that looks like another as there is only so 
much you can do to make them distinguished from each other – but on a car I 
thought it was weird.

Joe


From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Jason 
Miller
Sent: Thursday, January 08, 2015 7:12 PM
To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
Subject: Re: Knowledgebase design in SNow is almost the exact design as the 
Knowledgebase in Remedy...

**
Ok, so it isn't just me that has thought I was looking at a Jaguar a few times? 
 :)

On Thu, Jan 8, 2015 at 3:54 PM, Joe D'Souza 
jdso...@shyle.netmailto:jdso...@shyle.net wrote:
**
I agree. Right up to the prefixes for incident, change, problem to name a few.

The Knowledgebase looked like a direct copy with almost the same status flow 
design.

It appeared to me like a Hyundai Sonata that tried to look like a Jaguar.

Joe


From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Saji 
Philip
Sent: Thursday, January 08, 2015 6:48 PM
To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
Subject: Re: Knowledgebase design in SNow is almost the exact design as the 
Knowledgebase in Remedy...

**

I even saw a SNOW product that our vendor is using and it looks eerily like a 
toned down version of Remedy.  Not all impressed...
On Jan 8, 2015 12:33 PM, Tanner, Doug 
doug.tan...@compass-usa.commailto:doug.tan...@compass-usa.com wrote:
**
They all do it, anyone remember Rem-Mail. Doug

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Joe 
D'Souza
Sent: Thursday, January 08, 2015 12:21 PM
To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
Subject: OT: Knowledgebase design in SNow is almost the exact design as the 
Knowledgebase in Remedy...

**
Exact same status values.

Couldn’t help wondering if BMC has a point or two about them having stolen 
design concepts.

Joe
_ARSlist: Where the Answers Are and have been for 20 years_
This email is subject to certain disclaimers, which may be reviewed via the 
following link. http://compass-usa.com/Pages/Disclaimer.aspx.
_ARSlist: Where the Answers Are and have been for 20 years_
_ARSlist: Where the Answers Are and have been for 20 years_
_ARSlist: Where the Answers Are and have been for 20 years_

_ARSlist: Where the Answers Are and have been for 20 years_
_ARSlist: Where the Answers Are and have been for 20 years_
_ARSlist: Where the Answers Are and have been for 20 years_

Private and confidential as detailed here: 
http://www.energytransfer.com/mail_disclaimer.aspx .  If you cannot access the 
link, please e-mail sender.

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