[ 
https://issues.apache.org/jira/browse/CAMEL-14795?focusedWorklogId=410295&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-410295
 ]

ASF GitHub Bot logged work on CAMEL-14795:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/Mar/20 14:16
            Start Date: 26/Mar/20 14:16
    Worklog Time Spent: 10m 
      Work Description: davsclaus commented on pull request #3683: CAMEL-14795: 
allow dynamic setting of token in order to be able to
URL: https://github.com/apache/camel/pull/3683
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 410295)
    Time Spent: 20m  (was: 10m)

> camel-mail: allow dynamic setting of token in order to be able to support 
> OAUTH
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-14795
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14795
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-mail
>    Affects Versions: 3.2.0
>            Reporter: Franz Forsthofer
>            Priority: Major
>             Fix For: 3.2.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> camel-mail uses java-mail. Meanwhile java-mail does support OAuth for imap 
> and smtp (see [https://javaee.github.io/javamail/OAuth2]). The OAuth access 
> tokens typically expire. The current camel-mail component does not allow to 
> dynamically read the password (=token), the password is fix set in the 
> configuration. Therefore it is not possible to update the password/token.
> We improve the camel-mail component so that it is possible to dynamically 
> read the user and password/token, so that the OAuth use case can be supported.
> Instead of setting the user and password on the configuration, you specify an 
> authenticator bean in the configuration.  The authenticator method 
> public PasswordAuthentication getPasswordAuthentication() 
> will be called dynamically whenever a user/token (or password) is needed for 
> connecting to the mail server.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to