We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If there is no Connect or service account token provided in the configuration, it can try to authenticate the op-cli with a biometric unlock.
There is no Connect or service account token in the configuration, but provider still can authenticate op-cli using biometric unlock.
Add additional check in the during provider initialization to cover the case when no Connect or service account token provided.
The text was updated successfully, but these errors were encountered:
volodymyrZotov
Successfully merging a pull request may close this issue.
Summary
If there is no Connect or service account token provided in the configuration, it can try to authenticate the op-cli with a biometric unlock.
Use cases
There is no Connect or service account token in the configuration, but provider still can authenticate op-cli using biometric unlock.
Proposed solution
Is there a workaround to accomplish this today?
Add additional check in the during provider initialization to cover the case when no Connect or service account token provided.
References & Prior Work
The text was updated successfully, but these errors were encountered: