-
Notifications
You must be signed in to change notification settings - Fork 10
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.
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
refactor: rock connection #764
Conversation
Quality Gate failedFailed conditions |
Codecov is failing, but it's a refactor of existing code. Can't find where it should have more tests. |
} | ||
}; | ||
private String getAuthHeader() { | ||
String auth = application.getUser() + ":" + application.getPassword(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
password?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is such that a request from rock can use the password to authenticate so we know if the proces (that armadillo started via rock) has access to the data (from that user)?
Kinda scary, is there not a toke we could use instead? Or a way to at least encrypt this? Or is the internal communication also SSL? Because untrusted R code might now abuse it? Or to go even further, we could simply use a session number to reconnect because the password doesn't add much security?
This is a refactor of the rock connection class, using the spring
RestClient
, rather than the (deprecated)RestTemplate
, as suggested by spring. This should prevent blocking calls and overall work more smoothly.Included apache in gradle, because default calls will go via jetty, which fails:
spring-projects/spring-boot#38960