Secure Connect - AD Issue

MarcM_26,

Would you confirm a couple things for me?
First is if you can confirm that you selected LDAP and not LDAP and Local?

Do you actually have an LDAP network? Sorry I had to ask. 

Lastly, if you have a small number of devices discovered across a minimal amount of networks you may consider uninstalling and reinstalling the tool, but select LDAP and local.

As far as your question, maybe via console access to the vm there might be some options, but I am not certain as to what they are.

Let me know if this helps.

Hi Chris,

I did select Ldap only, We are using AD and when selecting the Test the test confirmed ok.

when trying to connect I have used the format DomainName/Userid, domainname\userid or even just userid, but i`ve been unable to login. I was hoping using a putty session to the appliance I would just be able to reset the login type to Local, or even local and Ldap so I could then test the Ldap logins again but also have the local option available too. 

The gateway has gone through a couple of upgrades and I was just hoping I would be able to reset the option instead of re-installing. 

Hi,

thank you for your feedback.

I am sorry that you have the effort to reinstall this instead of resetting.

Regards Martin

Have the same/similar issue. We conigured using "LDAP only" and the account used for LDAP connection expired so we're unable to login. Is there any way of either restoring local login or updating the account password through the console seeing that we have root access through putty?

Hello CarlAAM,

I have to do some research. I see a way to reset password if not using LDAP.

I want to confirm; are you using Secure Connect Gateway - Virtual Edition and what version?

Hello CarlAAM,

I have not found  a way to reset that password.  I do see requested feature enhancement for it.

At this time you would need to reinstall. 

A fix or workaround may come out in next version but I do not have concrete statements that it will or when the next release will be.