Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
You may experience some slow load times, errors, and slight inconsistencies. We ask for your patience as we finalize the launch. Thank you.

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

EDI contact search for non-domain member PC's.

I understand using EDI contact search utilizes your AD credentials you've used to login to your PC. What is the best way to handle contact search for PC's that are not domain members (ie: home PC's connecting via VPN)?

Is this an argument for choosing UDS over EDI? Is it ok to specify a read-only AD user account in the jabber-config.xml file to use for EDI?

Thoughts and opinions are welcomed!

Thanks,

Ryan

  • Jabber Clients
Everyone's tags (4)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

EDI contact search for non-domain member PC's.

Since you can configure site specific profiles via the device config, you can configure a special .xml file for those users, and configure a read only user as you mention, to bind to the AD and not use the windows credentials.

Just change this one:

UseWindowsCredentials to 0 and configure ConnectionUsername and ConnectionPassword.

Even the documentation says it should be a read-only user

Important: Cisco  Jabber for Windows does not encrypt the credentials that you  specify in a configuration file and writes the credentials to a log file  as plain text. If you specify credentials in a configuration file, you  should use a shared, read-only directory account that all Cisco  Jabber for Windows users can use.

http://www.cisco.com/en/US/partner/docs/voice_ip_comm/jabber/Windows/9_0_1/b_jabber_win_icg_chapter_0100.html

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
5 REPLIES
Cisco Employee

EDI contact search for non-domain member PC's.

Since you can configure site specific profiles via the device config, you can configure a special .xml file for those users, and configure a read only user as you mention, to bind to the AD and not use the windows credentials.

Just change this one:

UseWindowsCredentials to 0 and configure ConnectionUsername and ConnectionPassword.

Even the documentation says it should be a read-only user

Important: Cisco  Jabber for Windows does not encrypt the credentials that you  specify in a configuration file and writes the credentials to a log file  as plain text. If you specify credentials in a configuration file, you  should use a shared, read-only directory account that all Cisco  Jabber for Windows users can use.

http://www.cisco.com/en/US/partner/docs/voice_ip_comm/jabber/Windows/9_0_1/b_jabber_win_icg_chapter_0100.html

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
New Member

EDI contact search for non-domain member PC's.

Hello,

I found myself in the exact same issue. I know this was post very long time ago, but if you know how I have to change de jabber-config xml file in order to permit that my non in domain users could use the jabber properly.

Please be so kind to let me know.

Regards

EDI contact search for non-domain member PC's.

Hi Maria,

You could add following parameters under the Directory node in xml file (admin guide):

 

    EDI

    0

    IP_ADDRESS

    SERVER_PORT

    username

    password

 

You can use Config File Generator if you need help with the xml file generation.

or if your AD is integrated with CUCM then simply use UDS as below:

 

    UDS

 

Thanks,

Maqsood

New Member

EDI contact search for non-domain member PC's.

Thank you so much Maqsood.

It worksss, this is great!!!

I  change de EDI integration for UDS adding the next xml file, so the user  will not search the credentials in the AD instead it will do the lookup  in the CUCM

  UDS

 

true

  presence

And  I add this XML file in the following file of each user outside the domain:

C:\Users\mrios\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\Config

EDI contact search for non-domain member PC's.

Hi Maria,

Instead of copying the xml file on each non-domain machine, you should really create a group configuration file for these set of users as Jaime mentioned in his post. You should then host the file on TFTP server.

When client starts it always attempts to download the xml configuration file from TFTP server. If a configuration file is available, it will download and overwrite the existing file. Please review following sections in admin guide to create and upload a group configuration file.

Create Group Configurations

Host Configuration Files

Please review Configure the Client section for a complete description of available configuration options.

Thanks,

Maqsood

2723
Views
5
Helpful
5
Replies