cancel
Showing results for 
Search instead for 
Did you mean: 

Configure ISA Server with Afaria and Active Directory integration

Former Member
0 Kudos

Hello,

I have an Afaria and SUP installation, with a Relay Server and ISA Server.

I've integrated Afaria with Active Directory and it works with Android devices. When I re-install de iphoneserver component with "Afaria server managed authentication" option, and try to enroll an iOS device it fails, I receive a message of incorrect enrollment code. In this moment Android enrollment works and it fails in iOS.

If I change the "Authentication Delegation" on the IAS server from "No delegation, and client cannot authenticate directly" to "No delegation, but client may authenticate directly", iOS enrollment works, authentication credentials are requested and the MDM profile is installed. Unfortunately, with this change on the ISA Server the Android enrollment fails. In this moment, when I try to enroll an Android device, authentication credentials are requested. After enter the autenthication credentials the user receive a message of incorrect credential. I know the credentials entered are correct because are de same that worked before the change on the ISA Server.

Thus, my mainly question is how i must configure ISA Server with the next options:

- "No delegation, and client cannot authenticate directly"

- "No delegation, but client may authenticate directly"

Can anyone help me?

Thanks in advance

Regards

Tags edited by: Michael Appleby

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member105680
Active Participant
0 Kudos

Hello Javier,

Based on the description of the issue I am not clear how you are passing user credential to Afaria? I recommend specifying the following format:

DomainName\Userid

Password

The domain name mush match domain listed under security page in Server Settings.

I suspect Android logic in Authentication is assuming same domain as your Enrollment Server where iOS is not. Specifying DomainName will take care of this, if this is the issue indeed.

Let us know.

Thanks,

Aziz

SAP Support