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
Here's a tricky bug: When you assign a tag "tag:hoopsnake" to your OAuth2 client, you can not mint authkeys for that tag, you must use a child tag. Everything else fails with requested tags [tag:hoopsnake] are invalid or not permitted.
Then you can only request authkeys for tag:hoopsnake-selfhosted or tag:hoopsnake-remote (or both!), but no combination of the two with tag:hoopsnake in it.
The text was updated successfully, but these errors were encountered:
Adding a couple files to highlight the differences in the HTTP requests between a working cURL based script and hoopsnake. I'm using OAuth creds that have device write permissions on a parent tag,
Here's a tricky bug: When you assign a tag "tag:hoopsnake" to your OAuth2 client, you can not mint authkeys for that tag, you must use a child tag. Everything else fails with
requested tags [tag:hoopsnake] are invalid or not permitted
.As mentioned, you have to use a child tag.
Say you have this tag structure:
Then you can only request authkeys for
tag:hoopsnake-selfhosted
ortag:hoopsnake-remote
(or both!), but no combination of the two withtag:hoopsnake
in it.The text was updated successfully, but these errors were encountered: