MyUW - Error Codes

Defined MyUW error codes

MYUW-001

MYUW-001 arises when MyUW expects but does not receive an HRS emplid for a user among the user attributes MyUW receives when the user logs into MyUW. This might be because the user does not have an identity in HRS at all. Or it might be because that HRS identity is not fully linked with the credentials (username and password) the user logged in with.

This error specifically means that MyUW did not receive the HRS emplid. MyUW cannot use identity information it does not receive. If the user has an HRS emplid and should have access to HRS integration via MyUW, then the problem in identity linking will need to be resolved by their identity provider (the campus providing their identity).

MYUW-002

MYUW-002 arises in some circumstances when MyUW issues a 403 Forbidden HTTP status code response.

This might mean the user really is not authorized to access whatever path or take whatever action they were trying to take. In this case, trying again with authorizations, authorization rules, and identity unchanged will not help.

Unfortunately, it also might just mean that MyUW got confused about who the user is and what attributes and authorizations they have. This might happen in the case of session expiration or transient failure of server-side modules. In this case, trying again may work around the problem.

Technically, this error specifically means that the root servlet context provided the UI for the 403 Forbidden HTTP response.. Not all applications rely upon the root context to provide this response in all cases, and so there are other 403 status responses that are not this specific case. MYUW-002 in part exists to disambiguate where the 403 status response experience is being generated to support troubleshooting.

MYUW-003

MYUW-003 arises in some circumstances when MyUW issues a 404 NOT FOUND HTTP status code response.

This might mean MyUW could not find whatever path or content the user requested because that content does not exist to find. In this case, trying again will not help.

Unfortunately, it also might just mean that MyUW got confused about who the user is and what attributes and authorizations they have, and so cannot find the requested content given the apparent authorizations of the user. This might happen in the case of session expiration or transient failure of server-side modules. In this case, trying again may work around the problem.

Technically, this error specifically means that the root servlet context provided the UI for the 404 NOT FOUND HTTP response.. Not all applications rely upon the root context to provide this response in all cases, and so there are other 404 status responses that are not this specific case. MYUW-003 in part exists to disambiguate where the 404 status response experience is being generated to support troubleshooting.

MYUW-004

MYUW-004 arises when the MyUW client code running in the user's browser requests the information it needs to render a widget, the server responds with an error, and so the client cannot render the widget. This is typically because the user does not have permission to access the widget (is not in its intended audience) or because the widget has been deleted from the server. Users can lose permissions to widgets through changes in Manifest group memberships, student or employee status, or other changes to their identity. MyUW shows MYUW-004 so that the user has an opportunity to notice that a widget previously in their layout has stopped working and choose to update their layout to remove it, thereby internalizing the change rather than content silently disappearing with no user involvement.