We currently do not have an autobind external auth test case. We should develop one.
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to new - Custom field type adjusted to defect - Issue priority set to: 3 - Issue tagged with: Easyfix
Metadata Update from @mreynolds: - Custom field reviewstatus reset (from new) - Issue set to the milestone: CI test 1.0
Metadata Update from @ilias95: - Issue assigned to ilias95
autobind is where we identify you through your process uid, and bind based on that. It uses the ldapi socket (ie filesystem) so it only works on a localhost. You can see https://pagure.io/lib389/blob/master/f/lib389/init.py#_1104 here is where we 'detect" if autobind is active, and we do a sasl EXTERNAL to the connection.
As an ldapwhoami command it would be:
ldapwhoami -H ldapi:// -Y EXTERNAL
http://directory.fedoraproject.org/docs/389ds/FAQ/ldapi-and-autobind.html
might help you.
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2225
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)