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
Is your feature request related to a problem? Please describe.
We have encountered a limitation with Box CLI that has been affecting certain use cases in our environment. Starting from a particular version, the Box CLI uses Windows Credentials for storing authentication details. This approach presents an issue when we are using SSH or WinRM for remote login sessions, as we cannot access Windows Credentials in these scenarios.
Describe the solution you'd like
As a result, we are unable to use Box CLI via SSH or WinRM, severely affecting our workflow. Could you please consider implementing alternative methods for passing authentication information, such as through environment variables or by directly specifying a configuration file? This flexibility would greatly improve the utility of Box CLI for remote operations.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
Hello @Mki-developer ,
Thank you again for reporting this issue. We are trying to constantly improve our tools, so we will take this into account.
So far we have created a internal ticket to address your request (SDK-3343).
We need to discuss it with the team and possibly plan it in our work schedule.
Thank you for agreeing to respond to the request.
About a month has passed since our last communication, have you decided when you will be able to handle it?
We've added it to our backlog, but we don't have it scheduled in our planned roadmap, which means we won't be able to implement it in the near future.
We will inform you as soon as this changes.
Is your feature request related to a problem? Please describe.
We have encountered a limitation with Box CLI that has been affecting certain use cases in our environment. Starting from a particular version, the Box CLI uses Windows Credentials for storing authentication details. This approach presents an issue when we are using SSH or WinRM for remote login sessions, as we cannot access Windows Credentials in these scenarios.
Describe the solution you'd like
As a result, we are unable to use Box CLI via SSH or WinRM, severely affecting our workflow. Could you please consider implementing alternative methods for passing authentication information, such as through environment variables or by directly specifying a configuration file? This flexibility would greatly improve the utility of Box CLI for remote operations.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: