Tuscany
  1. Tuscany
  2. TUSCANY-3735

binding.atom can't connect to Apache Tuscany blog Atom feed

    Details

      Description

      The feed-aggregator and feed-aggregator-webapp samples use the Apache Tuscany blog Atom feed as one of the aggregated Atom feeds. Attempting to read from the Tuscany blog feed fails with the following error:

      [java] - Unable to respond to any of these challenges:

      {googlelogin=GoogleLogin realm="https://www.google.com/accounts/ClientLogin", service="blogger"}

      The problem is caused by code in the binding-atom-abdera module that always attaches a hard-wired HTTP Basic Authorization header with userid=admin and password=admin to all the HTTP requests that are sent. This header isn't acceptable to the the Tuscany blog feed.

        Activity

        Hide
        Simon Nash added a comment -

        As a workaround to get the feed-aggregator and feed-aggregator-webapp samples working, I've added code under revision r1025934 to avoid using HTTP authorization or authentication by default. (Both of these were causing the GET to fail.)

        I'm leaving this JIRA open to track the issue that we don't have a way for the user to control whether authorization and/or authentication are used when retrieving a feed.

        Show
        Simon Nash added a comment - As a workaround to get the feed-aggregator and feed-aggregator-webapp samples working, I've added code under revision r1025934 to avoid using HTTP authorization or authentication by default. (Both of these were causing the GET to fail.) I'm leaving this JIRA open to track the issue that we don't have a way for the user to control whether authorization and/or authentication are used when retrieving a feed.
        Hide
        Simon Nash added a comment -

        Merged the workaround into the 1.x trunk under revision r1027705 and into the 2.x trunk under revision r1027710.

        Show
        Simon Nash added a comment - Merged the workaround into the 1.x trunk under revision r1027705 and into the 2.x trunk under revision r1027710.
        Hide
        Simon Nash added a comment -

        The problem scenario described by this issue is now fixed, so I'm marking this issue as resolved in 1.6.1, 1.x and 2.x. If authentication/authorization support is needed for some other scenario, a new JIRA should be created to track this.

        Show
        Simon Nash added a comment - The problem scenario described by this issue is now fixed, so I'm marking this issue as resolved in 1.6.1, 1.x and 2.x. If authentication/authorization support is needed for some other scenario, a new JIRA should be created to track this.

          People

          • Assignee:
            Unassigned
            Reporter:
            Simon Nash
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development