Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-8979

[fiware-stackoverflow] FIWARE CEP (Proton) REST ouput authentication error

    Details

      Description

      Created question in FIWARE Q/A platform on 16-12-2015 at 11:12
      Please, ANSWER this question AT https://stackoverflow.com/questions/34309689/fiware-cep-proton-rest-ouput-authentication-error

      Question:
      FIWARE CEP (Proton) REST ouput authentication error

      Description:
      I'm training to send an output event from FIWARE CEP (Proton), using the REST consumer, to an ActiveMQ queue. The credential for access the ActiveMQ queue are included in the URL, as http://user:passwrd@X.X.X.X:xxxx/api/message/myqueue, but I have the following error:

      com.ibm.hrl.proton.webapp.resources.EventResource submitNewEvent
      INFO: events sent to proton runtime...
      org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme
      INFO: basic authentication scheme selected
      org.apache.commons.httpclient.HttpMethodDirector processWWWAuthChallenge
      INFO: No credentials available for BASIC 'ActiveMQRealm'@X.X.X.X
      com.ibm.hrl.proton.server.executorServices.SimpleThreadFactory$ProtonExceptionHandler uncaughtException
      SEVERE: Uncaught exception in thread: Thread[4,5,main],exception: com.ibm.hrl.proton.adapters.rest.client.RESTException: com.ibm.hrl.proton.adapters.rest.client.RESTException: Could not perform POST of event instance: ...
      with request headers:
      Content-Type: text/plain
      User-Agent: Jakarta Commons-HttpClient/3.0
      Host: X.X.X.X:xxxx
      Content-Length: 389
      to consumer http://user:passwrd@X.X.X.X:xxx/api/message/myqueue, responce result: 401

      Seems like that Proton doesn't extract the credential from the URL.
      Anyone else had the same problem?

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        2h 55m 1 Backlog Manager 22/May/17 6:08 PM
        In Progress In Progress Closed Closed
        3h 1 Backlog Manager 22/May/17 9:08 PM

          People

          • Assignee:
            backlogmanager Backlog Manager
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: