Application having issues connecting using Kerberos authentication

Andrew Maxwell shared this problem 3 months ago
Solved

I have two mongod daemons running on different ports on one server. I am able to successfully connect to the one running on port 27017 using Kerberos authentication, but cannot to the one running on port 27018. Both are setup the exact same way as both are in the same Ops Manager project. The only difference is that the one running on port 27017 is version 3.6, and the one on port 27018 is version 4.0. When I try to connect to the one on port 27018, it acts like it authenticates, but I can see the "Connecting" popup continuously flashing on the screen. Below are the errors I see in the log when the connection attempts are happening. I should note that I can successfully connect to both instances using other tools including the mongo command line utility.


2019-08-29T15:51:08.337-0500 I NETWORK [conn10359] received client metadata from <ip address>:<port> conn10359: { driver: { name: "nodejs", version: "3.1.7-1" }, os: { type: "Windows_NT", name: "win32", architecture: "x64", version: "10.0.17134" }, platform: "Node.js v10.2.0, LE, mongodb-core: 3.1.6", application: { name: "NoSQLBoosterV5_155140.954" } }

2019-08-29T15:51:08.343-0500 E ACCESS [conn10359] GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Mechanism is incorrect)

2019-08-29T15:51:08.344-0500 E ACCESS [conn10359] Was not able to acquire principal id from Cyrus SASL: -6

2019-08-29T15:51:08.344-0500 I ACCESS [conn10359] SASL GSSAPI authentication failed for on $external from client <ip address>:<port> ; AuthenticationFailed: SASL(-13): authentication failure: GSSAPI Failure: gss_accept_sec_context

2019-08-29T15:51:08.344-0500 E ACCESS [conn10359] Was not able to acquire principal id from Cyrus SASL: -6

2019-08-29T15:51:08.346-0500 E ACCESS [conn10360] GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Mechanism is incorrect)

2019-08-29T15:51:08.346-0500 E ACCESS [conn10360] Was not able to acquire principal id from Cyrus SASL: -6

2019-08-29T15:51:08.346-0500 I ACCESS [conn10360] SASL GSSAPI authentication failed for on $external from client <ip address>:<port> ; AuthenticationFailed: SASL(-13): authentication failure: GSSAPI Failure: gss_accept_sec_context

2019-08-29T15:51:08.346-0500 E ACCESS [conn10360] Was not able to acquire principal id from Cyrus SASL: -6

2019-08-29T15:51:08.346-0500 E ACCESS [conn10361] GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Mechanism is incorrect)

2019-08-29T15:51:08.347-0500 E ACCESS [conn10361] Was not able to acquire principal id from Cyrus SASL: -6

2019-08-29T15:51:08.347-0500 I ACCESS [conn10361] SASL GSSAPI authentication failed for on $external from client <ip address>:<port> ; AuthenticationFailed: SASL(-13): authentication failure: GSSAPI Failure: gss_accept_sec_context

2019-08-29T15:51:08.347-0500 E ACCESS [conn10361] Was not able to acquire principal id from Cyrus SASL: -6

Comments (3)

photo
1

Thank you for your feedback.

We have worked out a new build to try to resolve this issue, please download and give it a try.

https://nosqlbooster.com/s3/download/releasesv5/nosqlbooster4mongo-5.1.15-beta.1.exe

photo
1

The new build resolved the issue. Thank you so much!

photo
1

Resolved in 5.2.1