Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

at_activate error message for duplicate enrollments could be more helpful #548

Open
cpswan opened this issue Feb 5, 2025 · 0 comments
Open
Assignees
Labels
bug Something isn't working

Comments

@cpswan
Copy link
Member

cpswan commented Feb 5, 2025

Describe the bug

If I try to perform an enrollment using the same --drx parameter as before then the error message doesn't really explain what's wrong.

[INFO] 2025-02-05 11:07:13.294357 | connection | Connected
[ERROR] 2025-02-05 11:07:14.323532 | atauth_enroll_response | Did not receive data response from enroll request
[ERROR] 2025-02-05 11:07:14.323580 | ENROLL | atauth_send_enroll_request: 1

Steps to reproduce

  1. First I enroll an atSign using at_activate enroll -a ${atsign} -s ${otp} -p noports -k ${home}/.atsign/keys/${atsign}_key.atKeys -d ${device} -n "sshnp:rw,sshrvd:rw"
  2. Then I try another enrollment with exactly the same parameters.

Expected behavior

An error message that states an enrollment already exists for that DeviceName (which could go on to suggest that if you need to recreate an APKAM key for a device then it should be revoked and then re-enrolled).

@cpswan cpswan added the bug Something isn't working label Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants