I agree that feature (aliasing existing login names) would certainly have
saved us a few bucks in terms of consulting time.
Out of curiosity, how much does it cost, or a more appropriate question may
be what is its pricing structure..
Joe
-----Original Message-----
From: John Baker
Sent: Saturday, February 26, 2011 9:40 AM Newsgroups:
public.remedy.arsystem.general
To: [email protected]
Subject: OIM (Oracle Identity Manage) and remedy
Joe,
You make the point perfectly: it costs more consulting time than an SSO
Plugin license to attempt such a project, and this is exactly why JSS
invented "user aliasing". The product doesn't care if your SSO usernames do
not match the AR System User form because you can assign rules to match
them. We've learnt that the process of onboarding SSO is often more complex
than installing it - at least with SSO Plugin - and username matching comes
up one in three times.
Indeed, OpenID requires two fields (the provider and the identifier), so if
you want to integrate AR System with Google Mail ("User opens their mailbox,
clicks an ITSM ticket link and signs in to service it without logging in")
then there's no other way to adequately solve the problem without such a
feature.
We're mulling a presentation at wwwrug this year, but in the mean time,
here's a video:
http://www.javasystemsolutions.com/jss/video/view/SSOPlugin-OpenID
John
--
Single Sign On for AR System
http://www.javasystemsolutions.com/jss/ssoplugin
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
