Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 3 replies
  • Subscribers 6 subscribers
  • Views 2793 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AD-authentication not working / saving password

Marcel Hoffmann

Hi there,

we built a cluster containing two UTM9 and are currently setting up several services. At first we created an authentication service with a bind and base dn. I've tested the authentication and everything seemed to work.

We built several groups (e.g. for vpn usage) but I wondered why my AD-Users can't log in.

So I went back to my authentication service and klicked again on "test" and now fail. I entered the password again, click test and pass. I can also do the example authentication of a domain user. But after saving and re-entering the authenticationserver propertys all tests fail again. It seems that the UTM doesn't save the bind dn-password.

I tried differend DCs, different BIND-DN-Users but I don't get past this error. All my other services using AD-auth also fail.

Any help is highly appreciated.

Thanks,

Marcel Hoffmann



This thread was automatically locked due to age.
  • 0

    We are experiencing the same problem. We are on firmware version 9.408-4.

    Apparently the user authentication still works for us with the user/password stored previously, so our VPN users are able to log on still.

    But if we want to change the user information for the authentication service, this works only until save and re-entering the information. Upon re-entering all tests fail.

    Is this a bug with the current firmware version?

    Best, Christian

  • 0 in reply to Christian Matz

    This is a known issue and will be fixed in the next release.

  • 0 in reply to Louis-M

    Ok it seems that the problem is not a general one because the AD authentication works e.g. with the proxy configuration.

    Currently the authentication only fails when testing it in the webinferface and when using the user portal. I didn't test the VPN-client itself so far.

    Let's wait for a new firmware.