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

Specifying key content will conflict with the default key path #116

Closed
dekobon opened this issue Jun 8, 2016 · 1 comment
Closed

Specifying key content will conflict with the default key path #116

dekobon opened this issue Jun 8, 2016 · 1 comment
Assignees
@indianwhocodes
Labels
bug enhancement

Comments

@dekobon
Copy link
Contributor

dekobon commented Jun 8, 2016

If the default key path (~/.ssh/id_rsa) exists, you can't specify private key content when using a ChainedConfiguration. You will get an error message like:

java.lang.IllegalArgumentException: Private key content and key path can't be both set
@dekobon dekobon mentioned this issue Jun 8, 2016
Merged
@dekobon dekobon closed this as completed in 0eb2426 Jun 8, 2016
@indianwhocodes indianwhocodes self-assigned this Apr 2, 2019
@indianwhocodes indianwhocodes reopened this Apr 2, 2019
@indianwhocodes indianwhocodes added bug and removed bug labels Apr 2, 2019
russelldb pushed a commit to russelldb/java-manta that referenced this issue May 22, 2019
Added Test Case for TritonDataCenter#116
08c6f12
@indianwhocodes
Copy link
Contributor

Fixed by #527

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@indianwhocodes indianwhocodes

Labels
bug enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dekobon @indianwhocodes