A password problem and a JHED identity problem are not the same thing.
If you know your JHED ID and can reach the appropriate official account environment, the issue may concern the password lifecycle rather than the identity itself. Current Johns Hopkins support guidance says that a created JHED password is generally active for 365 days before expiration and that users can also change a password before it expires.
Because security requirements can change, users should always follow the current official workflow rather than relying on an old screenshot or copied instructions.
When a password change may be required
A password change can be relevant when:
- the current password has expired;
- the user has been notified that a change is required;
- the user wants to change a still-active password for security reasons;
- the account-access process directs the user through an official password-management workflow.
A password reset should not be treated as the universal solution to every access problem.
If you successfully authenticate but receive an access-denied message from a specific application, the problem may instead involve authorization.
Current password rules
Johns Hopkins support documentation currently describes several requirements for changing a JHED password, including length and character requirements, restrictions on reusing recent passwords and restrictions on including the JHED ID or parts of the user’s name. The exact rules should be checked against the current official password-change page before making an account change.
Password expiration can look like a system outage
A user may see an authentication problem and conclude that:
“JHED is down.”
But if the identity is valid and the password has expired, the problem is more accurately a credential-lifecycle issue.
Similarly, changing a password will not necessarily solve an application-permission problem.
A useful troubleshooting sequence is:
Do I know my JHED ID?
↓
Can I authenticate successfully?
↓
Is the password expired or otherwise the issue?
↓
Does the failure happen across multiple systems or only one application?
The answers can identify whether the problem is identity, authentication or authorization.
Changing a password is different from first-time setup
New users should also distinguish between:
- establishing a JHED account for the first time;
- changing an existing password;
- recovering access after an authentication problem.
These workflows can require different official procedures.
Never enter a JHED password into an unofficial site
A third-party article can explain the account ecosystem, but it should never request:
- your current password;
- a replacement password;
- a one-time MFA code;
- identity-verification data.
Account changes should only occur through verified official Johns Hopkins systems.
Internal Link Suggestions:
- JHED Account Setup for New Students and New Employees
- JHED Access Problems: Find the Failing Layer First
- How JHED Authentication Works Across Hopkins Systems
Sources: Johns Hopkins myJH Support.