[HELP-5363] FIWARE.Question.Tech.Data.BigData-Analysis.Cygnus oauth token refresh - JIRA

Details

Type: Monitor
Status: Closed
Priority: Major
Resolution: Done
Affects Version/s: None
Fix Version/s: 2021
Component/s: FIWARE-TECH-HELP
Labels:

Source URL:
http://stackoverflow.com/questions/32422551/cygnus-oauth-token-refresh
HD-Chapter:
Data
HD-Enabler:
Cosmos

Description

Created question in FIWARE Q/A platform on 06-09-2015 at 12:09
Please, ANSWER this question AT http://stackoverflow.com/questions/32422551/cygnus-oauth-token-refresh

Question:
Cygnus oauth token refresh

Description:
I'm using a cygnus build from source (latest release 0.8.2).
I've configured it to send orion subscriptions to cosmos.lab.fi-ware.org.
If I use only cosmos-user and cosmos-password it fails:

2015-09-06 12:21:27,063 (SinkRunner-PollingRunner-DefaultSinkProcessor) [ERROR - com.telefonica.iot.cygnus.sinks.OrionSink.process(OrionSink.java:143)] Persistence error (The /user/victor/queries/def_servpath/customer__36_productquerysalamanca directory could not be created in HDFS. HttpFS response: 503 Service unavailable)

So I have to use oauth-token. In this way it works successful, but my question is, in this scenario should I refresh manually access-token and change agent.conf file?

Thanks in advance

Activity

Descending order - Click to sort in ascending order

Fernando Lopez made changes - 27/May/21 10:57 AM

Fix Version/s

2021 [ 12600 ]

Manuel Escriche made changes - 12/Apr/16 9:01 AM

HD-Enabler		Cosmos [ 10872 ]
HD-Chapter		Data [ 10838 ]

Manuel Escriche made changes - 16/Dec/15 4:59 PM

Summary