Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bnc#965311 - yast ldap-server-ssl-check does not handle ldaps only ldap+starttls works #25

Closed
wants to merge 7 commits into from

Conversation

varkoly
Copy link
Contributor

@varkoly varkoly commented Mar 3, 2016

lc.bind();
exit(0);
} catch (LDAPException e) {
if (e.getResultCode() == 49) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not 42?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no error code 42. Error codes between 37 and 47 are not used.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

42, 37, 49, 47 are meaningless numbers. INVALID_CREDENTIALS is what makes code understandable.

/usr/include/LDAPResult.h:        static const int INVALID_CREDENTIALS            = 49;

@mvidner
Copy link
Member

mvidner commented Mar 29, 2016

That's strange, have you reverted the changes by accident? GitHub shows a nearly empty diff.

@@ -1,5 +1,7 @@
require "yast/rake"

Yast::Tasks.submit_to :sle12sp1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is wrong. It is commit only for SLE12SP1 maintenance branch. Please revert this change.

@teclator
Copy link
Contributor

teclator commented Apr 5, 2017

@varkoly, replacing this PR with #34

@teclator teclator closed this Apr 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants