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.

Sign up for GitHub

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

Jump to bottom

fcli ssc token list -u user -p pass --url url -> remaining usage -1 // MAC #194

Closed
xakrurychle opened this issue Dec 14, 2022 · 2 comments
Closed

fcli ssc token list -u user -p pass --url url -> remaining usage -1 // MAC #194

xakrurychle opened this issue Dec 14, 2022 · 2 comments

Comments

@xakrurychle
Copy link

xakrurychle commented Dec 14, 2022 •
edited
Loading

Screenshot 2022-12-14 at 12 38 42

remaining usage appears to be -1 though in SSC its like this
Screenshot 2022-12-14 at 12 39 48
@xakrurychle xakrurychle changed the title fcli ssc token list -u user -p pass --url url -> remaining usage -1 fcli ssc token list -u user -p pass --url url -> remaining usage -1 // MAC Dec 14, 2022
@rsenden
Copy link
Contributor

rsenden commented Dec 14, 2022

SSC 'Days to Expiration' corresponds to the token terminal date as displayed by SSC. Apparently, the SSC backend additionally allows for having tokens that can be used only a certain number of times (independent of expiration date), with -1 indicating that the token can be used for an unlimited amount of times. Since this information is not displayed in SSC, we should probably remove it from fcli (table) output as well to avoid confusion.

rsenden added a commit that referenced this issue Dec 14, 2022
@rsenden
fix: fcli ssc token: Make output more consistent with SSC UI (fixes #…
35523cc 
…194)
@xakrurychle
Copy link
Author

retested on v1.0.1, fixed

@github-actions github-actions bot mentioned this issue Aug 13, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rsenden @xakrurychle