Santosh I think there's some confusion. Neither of your scenarios require an SSO solution.
1. Blank password in User form This is one part of the AR System configuration to send an authentication event to an AREA plugin. Whether that's a link to an SSO solution or an LDAP solution. 2. Password set in User form This represents a standard AR System user account and tells AR System not to do (1) above. If your only requirements are for users to login with a Windows username/password or with a fixed AR System account, then you don't need an SSO solution. But just to clarify your point, the JSS SSO Plugin supports a fixed AR System user account and always has done, because it's an AR System feature not an SSO Plugin feature. There is of course very little reason to have them, fixed admin users being the common case, because SSO Plugin includes technology to validate a Windows username/password against a Windows Domain Controller without the need for an LDAP plugin. However if you want to use an LDAP plugin with SSO Plugin, that's fine. Further more, the JSS SSO Plugin Java AREA plugin (new in version 4) supports the BMC AREA LDAP plugin in a chained fashion, which is not supported by AtriumSSO. So if you're a fan of the Windows User Tool and you want to login with your Windows credentials, or even with an SSO enabled WUT, BMC provide no solution. Finally, in case you're not aware, AtriumSSO (being OpenAM) does not contain a fully featured Windows Authentication plugin, hence many BMC customers (and we keep finding them - or rather, they find us) are struggling to get a reliable "open IE and sign in to ITSM without logging in" solution with AtriumSSO. Ultimately, I guess you get what you pay for... John http://www.javasystemsolutions.com/jss/ssoplugin _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
