cloud-idp-password-reset

Reset Okta, Microsoft Entra, or Google Workspace passwords and clear stale local authentication state.

Updated May 6, 2026
One-click install
npx skills add https://github.com/idemeum/skills --skill cloud-idp-password-reset
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-idp-password-reset
Source: https://github.com/idemeum/skills/tree/main/cloud-idp-password-reset
Command: npx skills add https://github.com/idemeum/skills --skill cloud-idp-password-reset

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves failed sign-ins after a password reset by resetting a user’s cloud identity provider (Okta, Microsoft Entra, or Google Workspace) password and then cleaning up stale local session state so apps stop prompting for the old password.

Core Features & Use Cases

  • Cloud/Portal Password Reset (SSPR/SSPR+Cloud): Guides the user to the correct reset path (IDP self-service portal or idemeum cloud-mediated reset for Entra/Google).
  • Stale Session Cleanup: Purges cached credentials, clears browser SSO cookies, resyncs the IDP agent, and repairs macOS Keychain entries when applicable.
  • Account Discovery & Validation: Detects the IDP and (when possible) the username/UPN candidates, then collects the correct login identifier only when needed to avoid reset failures.

Use Case: A user changes their Entra/Okta/Google password, but Outlook, VPN, or Teams keeps asking for the old password; run this Skill to reset the correct cloud account and clear local artifacts tied to the previous password.

Quick Start

Run cloud-idp-password-reset when the user says they need to reset their Okta/Entra/Google password or their apps are still requesting the old password after the reset.

Frequently Asked Questions about cloud-idp-password-reset

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix apps prompting for the old password after a Microsoft Entra reset?

Cloud SSO password reset involves changing your identity provider credentials and purging stale local session state. It resolves failed sign-ins by clearing cached credentials, browser SSO cookies, and repairing macOS Keychain entries so apps stop prompting for outdated passwords.

Why does Outlook or Teams keep asking for my old Okta password after I changed it?

Yes, this password reset process supports Okta, Microsoft Entra, and Google Workspace. It uses IDP detection to identify your specific identity provider and applies the appropriate SSPR or cloud-mediated reset path for each platform.

How do I clear cached SSO credentials and macOS Keychain entries after a password reset?

Stale session cleanup is needed after a password change because local artifacts like browser SSO cookies and cached credentials retain outdated authentication state. Without removing these artifacts, apps continue prompting for the old password and fail to establish new SSO sessions.

Does this SSO password reset workflow support Google Workspace and Okta?

IDP detection and username validation identify the correct identity provider and account before initiating a cloud password reset. This ensures the reset targets the right IDP and collects the correct login identifier only when needed to prevent reset failures.

What is the best way to reset a cloud SSO password and refresh browser sessions?

This password reset workflow operates without directly handling user passwords. It guides users through the IDP self-service portal or cloud-mediated reset paths and enforces a non-password-handling workflow to maintain security compliance.

When should I run a cloud identity provider password reset to fix sign-in issues?

To clear cached SSO credentials and repair macOS Keychain entries, run a post-reset cleanup process. This purges local authentication state, repairs Keychain entries, resyncs the IDP agent, and removes stale browser SSO cookies tied to the previous password.