[jira] [Commented] (CAMEL-12443) camel-salesforce - Ability to use 'key' directly instead of pointing resource for generateJwtAssertion

["Zoran Regvart (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-12443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439079#comment-16439079 ] 

Zoran Regvart commented on CAMEL-12443:
---------------------------------------

Hi [~atyurin], thank you for raising this issue. Can you explain what content would be set in the {{keyValue}} in your example? I'm assuming PKCS#8 or SSLeay encoded RSA key? And why using {{KeyStore}} via {{KeyStoreParamters}} doesn't work in your case?

> camel-salesforce - Ability to use 'key' directly instead of pointing resource for generateJwtAssertion
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-12443
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12443
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-salesforce
>    Affects Versions: 2.21.0
>            Reporter: Andrey Tyurin
>            Assignee: Zoran Regvart
>            Priority: Major
>
> Hello,
> Could you extend the way of using JWT OAUTH2.0 authorisation for Salesforce component? For the current moment it uses resource uri (path to file, classpath, URL), but we want to use key directly (from String variable):
> String generateJwtAssertion() {
> ...
>     PrivateKey key = (PrivateKey) keystore.getKey(alias, keyStoreParameters.getPassword().toCharArray());
> ....
> We would like to have possibility to set the key directly from String variable, so there will be new way how to configure JWT for SF:
> String keyValue="This is some key content";
> SalesforceLoginConfig loginConfig = new SalesforceLoginConfig();
> loginConfig.setKey(keyValue);       <-------------- new option
>  
> Thanks,
> Andrey 
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)