The issue was resolved on Monday afternoon after being reported by a user in Australia on Monday morning (US time). The root cause is a long story, but the short version is that a data file was run incorrectly and caused all users without Supervisors assigned to error out. After the fix was applied on Monday afternoon, the users who were affected could log onto JDU just fine. This issue will not happen anymore, even if the person does not have a Supervisor assigned.