Carl,

Thank you for the explanation. Is the same true for Atrium SSO - that the 
Remedy user's password needs to be blank?

Sandra Hennigan
Remedy Developer

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Carl Wilson
Sent: Monday, April 01, 2013 7:29 AM
To: [email protected]
Subject: Re: AREA - ITSM 8.1 - can not make it work!

Hi,
A couple of things to note here.

1.  If you supply a password in ARS, this will be what is authenticated 
against.  To trigger an external authentication method you need to remove the 
password in ARS for that user - which in turn uses the "Cross Reference Blank 
Passwords" setting and the Authentication Chaining methods configured.
2.  Always have a user with a password set, such as an Administration account, 
so when external authentication does not work you can get back into the system 
(Demo is normally blank, as is appadmin).
3.  The Bind user for the AD credentials needs to be the fully qualified user 
from AD (CN, OU, DS, etc), not just the short user name.
4.  The Authentication Chaining is dependent on the password being supplied in 
the ARS configuration to how it behaives, this is explained in the guides.  It 
is recommended to not set the Authentication Method in earlier versions of ARS 
as it used to introduce instability, but I believe that has been rectified.  
You can play with the options once AREA is setup and working to see the 
different results, but for now I would leave it as "Off" to get started.
 
Kind Regards,
 
Carl Wilson
 
http://www.missingpiecessoftware.com/

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Dan Miller
Sent: 01 April 2013 11:26
To: [email protected]
Subject: AREA - ITSM 8.1 - can not make it work!

Hi all

i have a clean build 8.1.  i am experimenting with AREA 8.1 in its simplest 
form, basically trying to authenticate the support staff against their local 
AD...  simple one might think, but no...   i have been fighting with it for a 
week now and seem to be getting no where fast.  I am going to try and list the 
symptoms and findings here in the hope that someone can help (why can the 
simplest form of AD integration not be simple a few check boxes to make work 
like in most apps with this feature, and bury the clever stuff that the 
minority might want!!)

1. I have created a test user in AD called “test user”, with a password of 
“Password1”, and a USERNAME=123456
2. I have created a people record called “Test User” with a ARS password of 
“Window5” , and a USERNAME=123456
3. Placed the AD user into the default USERS container to avoid any confusion 
of OU’s
4. Tested both users in their own environment to make sure they log in
5. Setup AREA form in its simplest form with 
    - hostname = AD server
    - port = 389 (confirmed AD is answering on this port via telnet to that 
port)
    - bind user is my own AD account which is domain admin
    - userbase = CM=Users,DC=DOMAIN                  (note this domain has only 
a single extension, i.e. where BMC is bmc.com, in this domain it would just be 
“bmc”)
    - User Search Filter = userPrincipalName=%\USER$
    - Group membership = None
    - everything else is default
6.In the EA tab::
    - RPC port = 390695
    - Cross ref blank pas = CHECKED
    - Auth string chaining = “AREA - ARS”


So, what happens…  
- If I log into remedy using 123456 and Window5 then it logs in fine as expected
- If I log into remedy using 123456 and Password1 then it will not authenticate

I then tried a few of the different chaining modes to see what would happen.  
None work except when I set it to:
- ARS – OS – AREA
At this point, I can now log into Remedy using EITHER the AD password or the 
ARS password.

First question, what is “OS” in the chaining policy?  I am assuming operating 
system, but what settings is it using, how is it getting those details, is it 
from some settings in the AREA form?  I ask this, as when I went into AREA form 
and mess-up up the search stings and what not, but the login using AD password 
STILL worked, so it is like it does not use AREA config for the OS chaining 
function.

I then fixed AREA config, but changed the “User Search Filter” to use 
“displayName” and then tested login using “TestUser” as login name with AD 
password, and it failed.  I tried then using the USERNAME again and it still 
worked!

I am now very confused, as the configuration of this in 8.1 DOES on paper look 
simple.  I turned logging of filter to finest but go nothing of i8ntrest…  it 
is like it is just not doing anything.  I am just wondering have I missed a key 
point… I know in 7.65 is was a lot harder, but in 8.x it is supposed to be 
simpler…  it installs the plugin as part of install etc, so I am just wondering 
is something broke, or am I being an idiot (I suspect the latter unfortunately)

Cheers
dan

_______________________________________________________________________________
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"

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

Reply via email to