docs(auth): add lifecycle/update/troubleshooting guidance to auth method pages

[harrison-akeyless]

Summary\n- add lifecycle sections inspired by SAML improvements to core auth method pages\n- add explicit Access Role association guidance\n- add update-workflow guidance for existing auth methods\n- add troubleshooting checklists for common auth failures\n\n## Updated pages\n- docs/Accessing Akeyless/access-and-authentication-methods/auth-with-email.md\n- docs/Accessing Akeyless/access-and-authentication-methods/auth-with-aws.md\n- docs/Accessing Akeyless/access-and-authentication-methods/auth-with-api-key.md\n- docs/Accessing Akeyless/access-and-authentication-methods/auth-with-gcp.md\n- docs/Accessing Akeyless/access-and-authentication-methods/auth-with-azure.md\n\n## Validation\n- pre-commit run --files on all edited files\n- gitleaks: pass\n- markdownlint: pass\n- cspell: pass\n- lychee: pass

Summary by CodeRabbit

• Documentation
  • Enhanced authentication method guides with new sections on associating methods with Access Roles across API Key, AWS, Azure, Email, and GCP authentication pages.
  • Added comprehensive troubleshooting sections covering common authentication failure causes for each method.

[coderabbitai]

Warning

Review limit reached

@harrison-akeyless, we couldn't start this review because you've used your available PR reviews for now.

Your plan currently allows 1 review/hour. Refill in 47 minutes and 17 seconds.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more review capacity refills, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1be313c3-5b59-4e1b-b94f-79cef6780310

📥 Commits

Reviewing files that changed from the base of the PR and between 145fd03 and 01cace3.

📒 Files selected for processing (6)

• docs/Accessing Akeyless/access-and-authentication-methods/auth-with-api-key.md
• docs/Accessing Akeyless/access-and-authentication-methods/auth-with-aws.md
• docs/Accessing Akeyless/access-and-authentication-methods/auth-with-azure.md
• docs/Accessing Akeyless/access-and-authentication-methods/auth-with-email.md
• docs/Accessing Akeyless/access-and-authentication-methods/auth-with-gcp.md
• docs/Integrations & Plugins/cli-reference/cli-ref-auth/index.md

📝 Walkthrough

Walkthrough

This pull request expands documentation for five Akeyless authentication methods by adding consistent guidance sections: "Associate with Access Roles", "Update an Existing [Method] Authentication Method", and "Troubleshooting" checklists. Changes apply uniformly across API Key, Email, AWS, Azure, and GCP authentication pages.

Changes

Authentication Method Documentation Expansion

Layer / File(s)	Summary
Credential-based authentication methods docs/Accessing Akeyless/access-and-authentication-methods/auth-with-api-key.md, auth-with-email.md	API Key and Email authentication pages add new sections covering how to associate methods with Access Roles, update existing methods via Console and CLI, and troubleshoot common failures (credential mismatch, key rotation, role association, profile configuration, password expiration, and two-factor issues).
Cloud provider authentication methods docs/Accessing Akeyless/access-and-authentication-methods/auth-with-aws.md, auth-with-azure.md, auth-with-gcp.md	AWS IAM, Azure AD, and GCP authentication pages add parallel guidance for role association, method updates (Console + CLI), and cloud-specific troubleshooting (workload identity validation, bounded fields, audience matching, credential validity, EC2 metadata service, and Access Role association).

---

🎯 1 (Trivial) | ⏱️ ~5 minutes

---

Suggested reviewers

• Avi-Akeyless
• EldadH89

---

🐰 Five auth paths now shine bright,
With roles and updates and troubleshoot in sight,
API and cloud providers aligned,
Docs so consistent and refined! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely summarizes the main changes: adding lifecycle, update, and troubleshooting guidance to authentication method documentation pages.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch v1.0_auth-pages-lifecycle-sections

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}