Jc troubleshoot auth
Skill TheJumpCloud/jc-cli/skills/skills/jc-troubleshoot-auth
Diagnose JumpCloud authentication issues for a user — check account status, MFA, groups, auth events, and policies using the jc CLIFrom its SKILL.md
npx -y skills add TheJumpCloud/jc-cli --skill jc-troubleshoot-authAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.3 KB, as published. Nobody here has run it
Troubleshoot JumpCloud Authentication
Systematically diagnose why a user can't log in to JumpCloud or a connected application.
Prerequisites
jcinstalled and authenticated (jc auth status)
Gather Information
Ask for:
- Username or email of the affected user (required)
- What they're trying to access (JumpCloud portal, SSO app, LDAP, RADIUS?)
- Error message they're seeing (if any)
Diagnostic Steps
1. Check account status
jc users get USERNAME -t
Look for:
activated: false = user hasn't activated their account yetsuspended: true = account is suspended by an adminaccount_locked: true = account is locked (too many failed attempts or manual lock)
If locked: jc users unlock USERNAME
If suspended: jc users update USERNAME --suspended false (if appropriate)
2. Check MFA status
From the user get output, check:
totp_enabled: Is TOTP/MFA configured?- If MFA is required by auth policy but not set up, the user can't complete login
To reset MFA: jc users reset-mfa USERNAME
3. Check group memberships
jc graph traverse --from user:USERNAME --to user_group -t
If the user is trying to access an SSO app, verify they're in a group that's bound to that app:
jc graph traverse --from user:USERNAME --to application -t
4. Check recent auth events
jc insights query --service all --last 24h --query "[?initiated_by.username=='USERNAME']" -t
Look for:
sso_auth_failedevents — indicates SSO login failuresuser_login_failed— indicates portal login failuressuccess: false— any failed operations- The
client_ipfield — is the user coming from an expected IP?
5. Simulate auth policies
jc auth-policies simulate --user USERNAME -t
If you know the user's IP:
jc auth-policies simulate --user USERNAME --ip THEIR_IP -t
This shows which conditional access policies would apply and whether they'd allow, deny, or require MFA.
6. Check the specific application (if SSO)
jc apps get APP_NAME -t
Verify:
- The app is active
- The user (or their group) is bound to the app via graph
Common Causes
| Symptom | Likely Cause | Fix |
|---|---|---|
| "Account not activated" | User never completed activation | Resend activation or reset password |
| "Account locked" | Too many failed attempts | jc users unlock USERNAME |
| "Account suspended" | Admin action | jc users update USERNAME --suspended false |
| "MFA required" but not set up | Auth policy requires MFA | User needs to enroll MFA, or reset with jc users reset-mfa |
| Can access portal but not app | Missing group/app binding | Check jc graph traverse --from user:USERNAME --to application |
| Denied by auth policy | IP/location/device restriction | Check jc auth-policies simulate output |
Escalation
If the above steps don't identify the issue:
- Check auth policy blast radius:
jc auth-policies blast-radius POLICY_NAME -t - Review all org auth policies:
jc auth-policies list --all -t - Check RADIUS/LDAP config if the user accesses network resources:
jc radius list -t/jc ldap list -t