Changelog
Back to All
fixed

ad-bridge-24-1-2

5 months ago by ReadMe API

June 2024

  • Agent: 24.1.2.638
  • Windows: N/A

Issues resolved

  • Solaris SRU66 - Support new cron pam modules.

    • Resolution: New pam modules were added in SRU 66 that were not know to AD Bridge(pam_unix_cred and pam_user_policy).

  • Install fails on Oracle Solaris 11.4 SRU 66.

    • Resolution: Installation on Oracle Solaris 11.4 SRU 66 now supported.

  • Installation no longer fails sporadically with LW_ERROR_ERRNO_EPIPE when configuring krb5.

  • Now when you changing the computer account password, the computer account password changes as expected.

  • Pbis-support package collection with --nopgo and --nogpagent flags do not work.

    • Resolution: Pbis-support package collection with --nopgo and --nogpagent flags were enabling each other. Now both options work independently.

  • On Solaris the lwsmd daemon shutdown Segfaults - Core dumps on reboot.

    • Resolution: On Solaris, the lwsmd daemon did not verify the individual services have shutdown before freeing resources. Extra validation has been added to confirm before they are freed.

  • The “No Kerberos credentials available” error message is in the syslog's error message level, when it should be in the syslog's informational message level.

    • Resolution: This error was safe to ignore when generated for root so the error level has been updated to reflect this. The error could still be relevant for non-root users at which point they would elevate the logging to debug auth issues.

  • Computer account password resets no longer fail if DC validation is enabled.

  • You can now upgrade from repos for Debian 12+ and Ubuntu 23.04+.

  • The lsa ad-get-machine-account command now displays a local time stamp in a human-readable format. There is a new line under the Last Change Time, that's lists as As Local Time: with a human-readable date and time format (for example, As Local Time: Tue May 7 10:38:37 2024).

  • We added timestamps to the install.sh and package logs.

  • For the issue where the local provider authentication doesn’t work, and you are not able to login with a local provider account, you must upgrade to version 24.1.2.