Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Unable to log into Communicator Login with Active Directory Users on Mobility client

    Have been having issues since installation of the Mobility server this summer.

    From the Mobility Client I can Provision and register the User using the Active Directory Username and Password just fine.

    Then once in the Client I get a Communicator Login pop up, I try using the same Active Directory Username and Password and the Login just pops back up asking for password. I have also tried using the SIP password, changeme and shoretel as the passwords. Still continues to pop up asking for Password.

    Now if I create a NON Active Directory user, I can Provision and register just fine, and I can log into the Communicator Login Pop up with the standard Client password and everything works as it is supposed too.

    So my question is there a feature or setting that needs to be changed for the Communicator Login feature on the Mobility client to allow the a specific password or to allow the use of the Active Directory User password?
    Last edited by czachariason; 01-03-2014, 11:45 AM.

  • #2
    A little more information, we are not running a SA100 either

    Comment


    • #3
      Do you have the AD/LDAP authentication setup in the Mobility router and checked the advanced settings to make sure they a set properly?

      Comment


      • #4
        Yes, again I can log into the Mobility client with the AD user and password, once I am in the client I can make calls, look thru directory, but when I go to try change the call handling features I get a Communicator Login to appear, I use the same AD user and password and the pop up keeps popping back up. I attached a photo of the Log in Popup

        When I use a NON AD user, I don't get this popup I am just automatically logged and in the features work
        Attached Files

        Comment


        • #5
          Greetings Czachariason,

          I am having a related issue. I integrated our Shoretel Director with Active Directory a long time ago and am just now playing with the communicator application for Windows.
          I login via AD to the Director Page. I login RDC to the Shortel Server via my AD login. Login to Shoretel Director using same AD credentials. But when I try to login remotely using desktop Shoretel Communicator - fails. Switch desktop communicator to a Shortel - Local account and communicator login works just fine.

          I wonder if the application even knows how to pass domain\user information? Even more, be able to handle the response.

          The failure response is extremely fast.

          ShoreTel 11.2
          Build 16.44.5000.0
          ShoreWare Director

          Comment


          • #6
            @Czachariason - what format are you using for the Communicator login? it should be <domain>\username
            @jdurrett - make sure you followed the AD integration steps exactly as stated. If you can login to Director with AD credentials but not with Communicator, then you missed a step in the integration process

            Comment


            • #7
              @Czachariason - what format are you using for the Communicator login? it should be <domain>\username
              @jdurrett - make sure you followed the AD integration steps exactly as stated. If you can login to Director with AD credentials but not with Communicator, then you missed a step in the integration process.

              Comment


              • #8
                Solution was our string, we had lower case "ldap" and this has to be capatilized to work correctly, does not make sense being other systems does not matter on capitalization, but anyways it is working now.

                Comment


                • #9
                  Originally posted by czachariason View Post
                  Solution was our string, we had lower case "ldap" and this has to be capatilized to work correctly, does not make sense being other systems does not matter on capitalization, but anyways it is working now.
                  This fixed it for me, and I did note when I originally entered the LDAP string (with "ldap" instead of uppercase) that it kept warning about the string being incorrect. However, my Director login with AD credentials worked okay, so I just ignored the warning. Communicator login with my AD creds would not retain the password however, instead asking for the password each time Communicator started up. Once I changed the "LDAP" portion string to uppercase, the warning when saving did not appear and now my Communicator logs in properly. So I guess following the formatting of their example string exactly is the way to go

                  Comment

                  Working...
                  X