JHED and myJH are related, but they are not the same thing

The terms JHED, myJH, and Johns Hopkins Enterprise Authentication often appear together, which can make the Hopkins web environment seem more complicated than it is.

A useful way to understand the relationship is to think of JHED as the identity and directory layer, while myJH acts as a central web entry point for many Hopkins resources.

Johns Hopkins describes myJH as an online front door to hundreds of Hopkins-related tools. The university also explains that users can search JHED, check email, manage passwords, and access their JHED profile through myJH.

What does JHED do?

The Johns Hopkins Enterprise Directory is an online directory containing information associated with members of the Johns Hopkins community.

It is also closely connected with authentication. Johns Hopkins support documentation explains that the JHED Login ID is used by many university resources to authenticate users.

This makes JHED more than a conventional people directory.

It can serve as part of the identity infrastructure behind access to Hopkins services.

What is myJH?

myJH is the broader web portal through which users can reach many Hopkins resources.

Johns Hopkins’ own materials describe myJH as a central access point for university applications and information. The university’s branding guidance also notes that users can search JHED, manage their password, check email, and access their myProfile information through myJH.

In practical terms, this means that someone may interact with JHED through the myJH environment rather than treating JHED as a completely separate destination.

Where does Enterprise Authentication fit?

Another term that appears in Hopkins documentation is Johns Hopkins Enterprise Authentication.

According to Johns Hopkins support information, Enterprise Authentication provides centralized authentication and single sign-on access to an increasing number of web-based applications. It uses the JHED Login ID and password.

The basic relationship can therefore be represented as:

JHED identity → Enterprise Authentication → protected Hopkins applications

And:

myJH → central web access point → Hopkins resources

These are related layers, rather than three names for exactly the same service.

Why single sign-on matters

One of the useful characteristics of centralized authentication is that a user may not have to independently authenticate to every protected application.

Johns Hopkins explains that, after authenticating through Enterprise Authentication, users can access resources protected by that authentication system during the browser session without signing in separately to every resource.

The exact behavior can vary by application and session configuration, so users should follow the access instructions provided by the specific Hopkins service.

JHED is more than a username

A common misunderstanding is to treat JHED as simply the short username someone types into a login screen.

The JHED environment also supports directory information and profile management. Johns Hopkins documentation describes JHED as a source for contact information and explains that users can control visibility settings for information associated with their profile.

This is why the term can appear in both identity-related and directory-related contexts.

How the systems relate to different users

The exact services available through JHED depend on a person’s role.

For example, Johns Hopkins guidance identifies different uses for students, faculty, staff, and alumni. Students may use JHED credentials for services related to email and registration, while faculty and staff may use JHED-based access for academic or workplace systems.

There is therefore no single universal list of applications that every JHED user can access.

What should you do if the terms are confusing?

Start with the name of the system you are actually trying to access.

If the instructions mention:

• JHED ID / JHED LID — they are referring to your login identity.
• myJH — they are referring to the central Hopkins web environment.
• Enterprise Authentication — they are referring to the centralized authentication layer.
• Hopkins ID — they are referring to a separate institutional identifier.

Keeping those roles separate makes the terminology much easier to understand.

A simpler mental model

Think of the Hopkins environment as several connected layers rather than one giant system.

JHED identifies you and maintains directory information.

myJH provides a central web entry point.

Enterprise Authentication handles centralized authentication for supported applications.

Individual Hopkins applications provide the actual academic, administrative, employee, or other service.

Once those roles are separated, references to JHED throughout Hopkins documentation become considerably easier to interpret.