Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-10924

camel-linkedin: If accessToken is set, other credentials should be unnecessary on Fuse-sb2 runtime

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • fuse-7.5-ER1
    • fuse-7.4-GA
    • Camel
    • None

      When testing the camel-linkedin quickstart I noticed that the userName, userPassword, clientId, clientSecret still need to be set to something for the component to work.
      For example this configuration works:

      <bean id="linkedinConfiguration" class="org.apache.camel.component.linkedin.LinkedInConfiguration">
	<property name="clientId" value="null"/>
	<property name="clientSecret" value="null"/>
	<property name="redirectUri" value="https://localhost"/>
	<property name="userName" value="null"/>
	<property name="userPassword" value="null"/>
	<property name="accessToken" value="very long but correct access token"/>
</bean>

      But it should be also possible for this to work:

      <bean id="linkedinConfiguration" class="org.apache.camel.component.linkedin.LinkedInConfiguration">
	<property name="redirectUri" value="https://localhost"/>
	<property name="accessToken" value="very long but correct access token"/>
</bean>

      This was fixed in ENTESB-10368 for camel-2.21. This issue is about cherry-pick this changes to camel-2.23 in order to work with Fuse-SB2 runtime

              johnpoth John Poth
              jbouska@redhat.com Jan Bouska
              Jan Bouska Jan Bouska
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: