dal/issues/166>
Thanks,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
//www.h5l.org/pipermail/heimdal-discuss/2016-October/48.html>
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
> Or what alternate backend do think is solid and stable and why? ;-)
> I am not planning to use ldap =;-)
With Heimdal 7.1, you can use LMDB as the backend, the same backend behind
OpenLDAP's back-mdb database storage.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas
ome.
If we want to help improve documentation, how can we go about it? Is
there a wiki somewhere that we can edit?
Adam Lewenberg
Personal email. hbh...@oxy.edu
Personal email. hbh...@oxy.edu
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
then get the problems I described. As noted in the title of the bug
report, this is an MIT/Heimdal interop issue.
Generally, I'd suspect that Heimdal should treat default_ccache_name as
equivalent to default_cc_name.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corpor
en an
issue on GitHub for this functionality to be added?
Thanks!
Warm regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--On Monday, August 20, 2018 2:12 PM -0700 Quanah Gibson-Mount
wrote:
In the MIT code, this is provided via:
GSS_C_SEC_CONTEXT_SASL_SSF
Is there something similar in Heimdal that I'm missing, or should I open
an issue on GitHub for this functionality to be added?
Ok, in reading the