We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
#inspect
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
Example:
c = Net::LDAP.new(conn_hash) p c => #<Net::LDAP:0x007ffc6698a9f8 @host="server-001", @port=636, @verbose=false, @auth={:method=>:simple, :username=>"cn=user,o=org", :password=>"supersecret"}, @base="dc=com", @force_no_page=false, @encryption={:method=>:simple_tls, :tls_options=>{}}, @instrumentation_service=nil, @open_connection=nil, @result=#<Net::LDAP::PDU:0x007ffc669895f8 @message_id=1, @app_tag=1, @ldap_controls=[], @ldap_result={:resultCode=>0, :matchedDN=>"", :errorMessage=>""}>>
This can be worked around when using this gem by wrapping Net::LDAP in another class, but I don't imagine this is desirable behavior.
Could something be done similar to GitHub's octokit gem (highlighted LOC here) to mask them (or remove entirely)?
The text was updated successfully, but these errors were encountered:
@astockwell that's a great suggestion! Would you be interested in opening up a PR with a test?
Sorry, something went wrong.
You got it 👍
b0bf551
Merge pull request #217 from astockwell/feature/obscure_auth
49c0265
obscure auth password upon #inspect, added test, closes #216
obscure auth password upon #inspect, added test, closes ruby-ldap#216
e75b03f
Merge pull request ruby-ldap#217 from astockwell/feature/obscure_auth
1f9bb0d
No branches or pull requests
Example:
This can be worked around when using this gem by wrapping Net::LDAP in another class, but I don't imagine this is desirable behavior.
Could something be done similar to GitHub's octokit gem (highlighted LOC here) to mask them (or remove entirely)?
The text was updated successfully, but these errors were encountered: