[
https://issues.apache.org/jira/browse/CAMEL-10826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-10826.
---------------------------------
Resolution: Fixed
Assignee: Claus Ibsen
Fix Version/s: 2.19.0
> camel-salesforce - Logging in as null
> -------------------------------------
>
> Key: CAMEL-10826
> URL: https://issues.apache.org/jira/browse/CAMEL-10826
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
> Affects Versions: 2.19.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Trivial
> Fix For: 2.19.0
>
>
> Notice this when starting Camel
> {code}
> 2017-02-14 11:22:57.352 INFO 15118 --- [ main]
> o.a.c.c.s.internal.SalesforceSession : Login user null at Salesforce
> loginUrl: https://login.salesforce.com/services/oauth2/token
> 2017-02-14 11:22:58.869 INFO 15118 --- [ main]
> o.a.c.c.s.internal.SalesforceSession : Login successful
> {code}
> We should likely change that null to something else. And also we should avoid
> logging the username at INFO level and only do that at DEBUG level. At INFO
> level we can mask the username using ******
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
