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

camel-linkedin: If accessToken is set, other credentials should be unnecessary

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • fuse-7.4-GA
    • fuse-7.3
    • Camel
    • None
    • Fuse 7.4 Sprint 45 - Dev #1

    Description

      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>

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-10923 [QUICKSTART] camel-linkedin quickstart is not working

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Done
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-10924 camel-linkedin: If accessToken is set, other credentials should be unnecessary on Fuse-sb2 runtime

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Done
          links to

          Web Link CAMEL-13341

          Activity

            People

              jondruse@redhat.com Jiri Ondrusek
              jkasztur@redhat.com Jan Kasztura (Inactive)
              Jan Bouska Jan Bouska
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: