Knowledge Partner
Knowledge Partner
215 views

AD Driver Version 3.5.16 - where are the corresponding package updates?

The following bugs are reported fixed in the latest AD driver (released
last thursday) but to get the bug fixes, we need an updated NOVLADDCFG
package. I've checked for package updates a few times and this package
update hasn't shown up for me. Has anyone else managed to get this new
package in Designer?

- Default code from AD driver's 4.0.1 package appears incorrect. Bug 710833
- sAMAccountName incorrectly sanitized due to invalid regex. Bug 717082

I know how to fix both bugs manually (I raised the second one), but am
wondering if anyone knows why the package update has been delayed?

Also.. AD driver not clearing stale entries from cache. Bug 710062 -
anyone got more details on this bug? (bug is not accessible to external
folk). Which cache are they referring to?
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: AD Driver Version 3.5.16 - where are the corresponding packageupdates?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Packages... good questions, and I've asked.

The cache, as I understand it, was the password sync cache on the domain
controller. The passwords, for users whose passwords would never
synchronize, would hang out there forever, or until they were eventually
synchronized. Unassociated users were the original example.

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPHXOhAAoJEF+XTK08PnB5v8cQAIu+9DvAxARwaasuAnXzMFQ8
1j/TpHhqfcdbdwAbWiSFqVzuQ7V/mWpRhvI3BomEYkudn6PsdOIP4KBof8+o8CcO
g6rb3LKhYppbFasyJQQ2UXN5MzdlsWIqdKqtRhGXf83C1I679GGvAKoK0eJxpqoi
XfSUuwtpVIZCUeHhvUlfbXwYCCRBnXSRNT8LvOpZFDIb3Q33WAp7w+PJyKBm3MSb
G36AXDM513O5y1tSHXzRHSWn4Bk6bfF/AivH9lfkWmhVa0NG1fZ58ozuFRl6cFx0
ip92eKB2dA3Rm9OhKzIjRIyJYcQSy64qJVGnG/s3FKYBY8lChOs8MXRxhqcpyXvV
XGt43re7+2rOHxlq45AQgRLplMqUdbySxvnvulJaMLVBjaqJkEUpUx98IpANkGt5
r/LoViVj6vvrKokBtIaKjWyKOSpNskrxGSIr4YyrysQFq+401Kdeu9oST1SZqFHN
xv+4zRxh1NqnrTIPdMJoR1093a6NVfriUCHS/U63JGDuijGiLOYTBR+0ao8ZPMHx
XVJYLFErwDJMIlhFsIVJGTX1kku0UOHUMI6Kc22eCpgCAN3RcvAijZDKlCCHyKzk
o9PByCszq6F9e4si4YffeJNsZHpw67341NoNtdsqItilsY5S5EuYp4KtsoERvTX7
XYfmIhtx3O7R0XgQOdwR
=j7tX
-----END PGP SIGNATURE-----
0 Likes
Knowledge Partner
Knowledge Partner

Re: AD Driver Version 3.5.16 - where are the corresponding packageupdates?

On 23.01.2012 15:50, ab wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Packages... good questions, and I've asked.


Thanks for chasing this up internally.

After a bit of a false start (where one bug wasn't fixed in all places
it appeared in policy) it seems these two packages are now available
from the beta repository and seem to work OK. Lets hope they make a
quick transition from beta to release.
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.