The OOB integration of Remedy with RKM sets it up so that you don't need to do this. What exactly are you trying to do? What it boils down to is that a session ID must be generated and stored for the given user in the KMS:Session form. This session ID then gets included in the query portion of the URL used to access RKM. When RKM sees this, it validates the session ID and IP address the user is coming from with the one stored in Remedy. If there is not already an IP address, it adds it to the groups field on the form. If the session ID is found in the form, and the IP address matches (if there was already one there), then it uses the login stored with that session ID as the login credential for that session.
Lyle -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Carin Grobler Sent: Thursday, June 03, 2010 8:10 PM To: arslist@ARSLIST.ORG Subject: RKM Authentication Hi, Has anyone integrated RKM with Remedy and managed to pass the current user information so it does not prompt for a user name every time. AR Server 7.1 patch 6 RKM 7.2 Carin _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are" NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
