[
https://issues.apache.org/jira/browse/CAMEL-17066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17427223#comment-17427223
]
Andrea Cosentino commented on CAMEL-17066:
------------------------------------------
There is already another mechanism for authentication
https://camel.apache.org/components/latest/nats-component.html#_configuring_username_and_password_or_token
We can support some other mechanism, but without over engineering the component.
Credential file could be one of them, have a look at how other component
implements this, by supporting file:, classpath:, http: for remote file etc.
> camel-nats - Support authentication with Nats server
> ----------------------------------------------------
>
> Key: CAMEL-17066
> URL: https://issues.apache.org/jira/browse/CAMEL-17066
> Project: Camel
> Issue Type: New Feature
> Components: camel-nats
> Reporter: Guillaume
> Priority: Major
>
> Nats server provides several ways to authenticate:
> * User / password
> * token
> * Nkey
> * credential files
> [https://docs.nats.io/developing-with-nats/security]
>
> I guess the token and user / password over an URI in camel wouldn't be very
> secure.
> Would the credential files be a valid implementation ?
> => provide a credentialsFilePath URIParam that is then used in the
> NatsConfiguration
>
> {code:java}
> @UriParam(label = "security")
> private String credentialsFilePath;
> ...
> io.nats.client.Options.Builder build = new Options.Builder();
> ...
> if (getCredentialsFilePath() != null) {
> builder.authHandler(Nats.credentials(getCredentialsFilePath()));
> }
> {code}
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
