DOCSP-48712 edit for proper user/pw info

[shuangela]

Pull Request Info

PR Reviewing Guidelines

JIRA - https://jira.mongodb.org/browse/DOCSP-48712
Staging - https://deploy-preview-480--docs-golang.netlify.app/connection-troubleshooting/
https://deploy-preview-480--docs-golang.netlify.app/usage-examples/

Self-Review Checklist

• Is this free of any warnings or errors in the RST?
• Did you run a spell-check?
• Did you run a grammar-check?
• Are all the links working?
• Are the facets and meta keywords accurate?

[netlify]

✅ Deploy Preview for docs-golang ready!

Name	Link
🔨 Latest commit	5b0ce40
🔍 Latest deploy log	https://app.netlify.com/sites/docs-golang/deploys/67e6e85a1ea6dd00080c80b4
😎 Deploy Preview	https://deploy-preview-480--docs-golang.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[mongoKart]

back to you with a question

[mongoKart]

Q: isn't this true about non-DB usernames and passwords too? Same question for line 113 in this file.

[shuangela]

Can connection strings contain non-DB username and pws? I was reading the golang connection guide that states that "the connection string contains your database username and, if you are using password-based authentication, your password," so I was under the impression that the connection string can only contain a db user and not any other type of user.

[mongoKart]

I was thinking of the enterprise auth mechanisms, which use Kerberos principal and LDAP username for the username parameter.

I would also hope that anyone coming to this page for help would recognize that username and password apply to them even if they're using their db username/password.

For those reasons, I'd vote to keep username and password for this troubleshooting section

[shuangela]

I'm fine with that! i'll change them back 👍 thanks for the explanation

[mongoKart]

LGTM!

[github-actions]

The backport to v1.17 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v1.17 v1.17
# Navigate to the new working tree
cd .worktrees/backport-v1.17
# Create a new branch
git switch --create backport-480-to-v1.17
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 da8780df22770b0793d1e1e04cef41c158b945b7
# Push it to GitHub
git push --set-upstream origin backport-480-to-v1.17
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v1.17

Then, create a pull request where the base branch is v1.17 and the compare/head branch is backport-480-to-v1.17.

[github-actions]

The backport to v2.0 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.0 v2.0
# Navigate to the new working tree
cd .worktrees/backport-v2.0
# Create a new branch
git switch --create backport-480-to-v2.0
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 da8780df22770b0793d1e1e04cef41c158b945b7
# Push it to GitHub
git push --set-upstream origin backport-480-to-v2.0
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.0

Then, create a pull request where the base branch is v2.0 and the compare/head branch is backport-480-to-v2.0.

[github-actions]

The backport to v2.1 failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.1 v2.1
# Navigate to the new working tree
cd .worktrees/backport-v2.1
# Create a new branch
git switch --create backport-480-to-v2.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 da8780df22770b0793d1e1e04cef41c158b945b7
# Push it to GitHub
git push --set-upstream origin backport-480-to-v2.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.1

Then, create a pull request where the base branch is v2.1 and the compare/head branch is backport-480-to-v2.1.