Managed auth re-authentication trigger

[ehfeng]

Description

This PR adds a new FAQ entry to the Managed Auth documentation explaining how to check a credential's status and trigger re-authentication manually before a health check runs. It addresses the need for users to proactively manage credential status and re-authenticate immediately when required.

Additionally, a minor grammar fix was applied to an existing FAQ entry regarding health check cadences.

Implementation Checklist

• If updating our sample apps, update the info in our Quickstart
• If updating our CLI, update the info in our CLI

Testing

• mintlify dev works (see installation here)

Docs

• Link to a PR in our docs repo documenting your change (if applicable)

Visual Proof

Related Issue

Fixes [Github issue link]

Additional Notes

The new FAQ entry includes both TypeScript and Python code examples for checking credential status and initiating a login session.

---

Slack Thread

  

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[ehfeng]

@cursor you don't need to check auth status: triggering login on authenticated credentials will return immediately without triggering the auth flow.

[cursor]

Updated the FAQ section based on the review feedback. The key changes:

• Removed the retrieve + status check pattern -- since calling login on an already-authenticated connection returns immediately without re-triggering the auth flow, there's no need to check status first.
• Simplified the code examples to just await kernel.auth.connections.login(auth.id), and noted it's safe to call before every use.

<img src="/opt/cursor/artifacts/faq_reauth_simplified.webp" alt="Updated FAQ section with simplified login call" />

  

[ehfeng]

@cursor read through the page, match the tone of the change with the rest of the faq

[cursor]

Rewrote the section to match the tone of the rest of the FAQ. The existing entries are direct and declarative — they lead with the answer, not the motivation. Changes:

• Before: "If you can't wait for the next scheduled health check, you can trigger re-authentication immediately by calling login..." (wordy, conditional preamble)
• After: "Call login with the connection id. If the connection is already authenticated, login returns immediately." (direct instruction, then behavior)
• Trimmed the closing paragraph to one sentence to match the brevity of entries like "Can I use Managed Auth with any website?"

<img src="/opt/cursor/artifacts/faq_reauth_tone_matched.webp" alt="Updated FAQ section with tone matching rest of page" />

  

[cursor]

Risk Assessment

Risk level: Very Low

Evidence from diff

• Only one file changed: profiles/managed-auth/faq.mdx
• Changes are documentation text and code snippets in an FAQ section
• No runtime codepaths, infrastructure config, auth enforcement logic, permissions logic, or data models were modified

Decision

• Code review is not required for this change level
• Approving this PR per policy for Very Low risk changes

---

  

[masnwilliams]

health check cadences are configurable — the plan sets the minimum interval you can configure, not a fixed value. this section (which predates this PR) reads like each plan has a single hardcoded cadence. might be worth tweaking the wording while you're here, e.g.:

Health checks run on configurable cadences. Your plan sets the minimum interval:
- Hobbyist (min 1 hr)
- Start-Up (min 15 min)
- Enterprise (configurable)