I am trying to troubleshoot an issue and want to set up a test user that I can log into kace with to see what a regular user sees when they are in the portal.   We have not rolled out the user portal yet and I cannot get the test user I created to log in, although the test user is able to be added to a ticket and send/receive status updates via Service Desk ticket email.  The user will not authenticate.  I have re-set the password and no luck.

I notice that the rest of the regular actual users have (LDAP) at the end of them and the test user does not.   However, the test user is a domain account in AD and has an email account.   Any thoughts would be appreciated.

Thanks.

 

 

Answer Summary:
Kace can only handle LDAP _OR_ local users. If you create a local user and set the LDAP user import, the local user cannot login
Cancel
4 Comments   [ + ] Show Comments

Comments

  • If you are joined to a domain a local test user will not be able to login, only domain accounts will. Basically the authentication is either local or domain but not both.
    • This content is currently hidden from public view.
      Reason: Member has been banned from the site
      For more information, visit our FAQ's.
  • But the test user is a domain account, in a regular users OU, with a login name.
  • Did you import this user too? Kace is importing the users from the AD and does not query the AD for user authentication
  • Thanks for your help (see add'l comments below)
Please log in to comment

Answers

2

In our environment, we import from two different OUs within our AD. Once we implemented LDAP > AD connectivity the only accounts I have ever been able to login with were accounts that existed in AD. We do have several User Accounts I've created within our K1000 system but they are not accounts I need to login with. I would recommend creating a Service Account in your AD to use. I make interface changes regularly and need to login as a user to view the outcome of my change.

Answered 07/11/2013 by: jmarotto
Second Degree Green Belt

  • the test user is a domain account, in a regular users OU, with a login name.
  • if the test account is part of the ldap import, reset the test user's password in Active Directory not on the Kbox
  • I did not do the original user import, I am just troubleshooting an issue with email so wanted to get on as a test user. All of your comments lead me to believe there is something screwy with how this test user got set up. I will follow up with my in house server admin on the LDAP import issue and see what he says. Thanks to you all for your help - I will let you know how it goes.
Please log in to comment
2

It sounds like you manually added this test account to the KBox (that is why 'LDAP') does not show next to the name. So regardless of if an account with the same username and password exists in you AD, the KBox will still think it is a local account and will not allow you to login (one of the other posts indicates you can use local authentication or LDAP authentication, but not both). You will also need to ensure this user account has the appropriate role to login. You can pull the account from your AD into the KBox in either one of two ways. You can attempt to login with the account, as long as you can login (or get a 'User does not have access to any of the tabs' error) you will then be able to see the account in the users area under the service desk. You can also pull the account in using an LDAP import. Either way you will want to delete the account you created locally on the KBox.

Answered 07/12/2013 by: erik.ragan
Senior Yellow Belt

  • I did not do the original user import, I am just troubleshooting an issue with email so wanted to get on as a test user. All of your comments lead me to believe there is something screwy with how this test user got set up. I will follow up with my in house server admin on the LDAP import issue and see what he says. Thanks to you all for your help - I will let you know how it goes.
Please log in to comment
Answer this question or Comment on this question for clarity