feat(service-provider-server): add kerberos addon MONGOSH-823 #942
Conversation
addaleax
changed the title
| try { | ||
| try { | ||
| try { | ||
| shell.assertContainsOutput('Unspecified GSS failure'); | ||
| } catch { | ||
| shell.assertContainsOutput('Error from KDC'); | ||
| } | ||
| } catch { | ||
| shell.assertContainsOutput('No credentials cache file found'); | ||
| } | ||
| } catch { | ||
| shell.assertContainsOutput('The logon attempt failed'); | ||
| } |
There was a problem hiding this comment.
Yeah, I’m not sure that this is actually exhaustive yet… but all of these indicate that the kerberos addon actually tried to do something :)
|
|
addaleax
force-pushed
the
823-dev
branch
4 times, most recently
from
cc0bf4f to
76d2ccf
Compare
| # executable compilation step. | ||
| npm --unsafe-perm=true run bootstrap-ci -- --scope @mongosh/build | ||
| npm --unsafe-perm=true run bootstrap-ci -- --scope @mongosh/cli-repl --include-dependencies || \ | ||
| (npm --unsafe-perm=true run bootstrap-ci -- --scope @mongosh/cli-repl --include-dependencies --ignore-scripts && npm --unsafe-perm=true run compile-cli) |
There was a problem hiding this comment.
For context: This was working with mongodb-client-encryption@1.2.3, because that included a deps folder with the necessary headers and library files to build a broken version of the addon (the library files were only actually working on x64 macOS, but they could still be linked on most platforms and we don’t need a functional mongodb-client-encryption addon to build the executable, only one with the proper source code + types)
…e krb error messages
This is WIP because it turns out there’s actually a conflict between theInitfunctions of the libmongocryptd bindings and the kerberos addon, because they are not declared asstatic. That’s something for tomorrow, though :)Tomorrow has happened and now that bug is gone thanks to the Node.js driver team :)