Having trouble changing your password and seeing a “request failed” message?
This article explains when password changes are possible, what might be causing issues, and what to do next.
Important Update
Catalyst now uses Microsoft Single Sign-On (SSO) for most environments.
If your Catalyst login redirects you to a Microsoft login screen, then passwords are managed by your organization—not by EBM—and you will not be able to change your password within Catalyst.
If You Use Microsoft SSO:
- You must update your password through your organization's Microsoft tools or IT helpdesk.
- Visit https://passwordreset.microsoftonline.com for self-service password resets.
- If you're signed in to other Microsoft services (e.g., Outlook), Catalyst will recognize your credentials automatically unless your session times out.
Still Seeing a Password Field in Catalyst?
If you are using a legacy Catalyst environment (non-SSO), and you're seeing a "request failed" message when attempting to change your password, here are some troubleshooting tips:
Common Causes and Fixes
1. Avoid Sequential Special Characters
Certain combinations—like using two special characters back-to-back (e.g., !!, $$)—can cause the password update to fail. Try using special characters in non-repeating, non-sequential ways.
2. Use a Diverse Mix of Characters
Create a password that includes:
- Uppercase and lowercase letters
- Numbers
- Special characters
Avoid predictable or repeated patterns.
3. Meet All System Requirements
Double-check that your password:
- Meets the minimum character length
- Includes at least one special character, number, and uppercase letter
- Doesn’t contain restricted or disallowed character patterns
4. Clear Your Browser Cache
Outdated cache or cookies can interfere with system behavior. Clear your browser cache, then try changing your password again.
5. Try a Different Browser
Occasionally, browser extensions or settings can interfere. Switching to another browser (e.g., from Chrome to Edge) can sometimes resolve the issue.
Still Having Issues?
If you’ve confirmed that you’re on a legacy (non-SSO) environment and the issue persists after trying the above, please contact EBM Support so we can help troubleshoot further or escalate as needed.
If you’re unsure whether your environment uses Microsoft SSO or legacy login, we’re happy to help confirm.
For all environments: remember to use a secure, unique password that isn’t shared across other systems or services. If you need assistance, contact us at support@ebmsoftware.com.
Comments
0 comments
Article is closed for comments.