You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not entirely sure if this is intended behavior or a bug, but when requesting pre-auth keys via the API /api/v1/preauthkey?user=<user>, the user field on the returned keys have emails and not the user.name or a user object.
API docs aren't clear on this and I expect the response to either return the user.name since that is what we use to filter for pre-auth keys in the request (?user=<user.name>). Or even better, it should return the entire user object, exactly the same as how /api/v1/node does.
Steps To Reproduce
Setup Headscale with OIDC
Authenticate via OIDC (creating an OIDC user in the database)
Generate a pre-auth key tied to the OIDC user
Request the auth keys tied to the OIDC user via the API.
Is this a support request?
Is there an existing issue for this?
Current Behavior
I'm not entirely sure if this is intended behavior or a bug, but when requesting pre-auth keys via the API
/api/v1/preauthkey?user=<user>
, theuser
field on the returned keys have emails and not theuser.name
or a user object.Example:
Expected Behavior
API docs aren't clear on this and I expect the response to either return the
user.name
since that is what we use to filter for pre-auth keys in the request (?user=<user.name>
). Or even better, it should return the entire user object, exactly the same as how/api/v1/node
does.Steps To Reproduce
Environment
Runtime environment
Debug information
status.json
debug_netmap.json
The text was updated successfully, but these errors were encountered: