Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Missing x-auth-token header in Configure the south bound protocol #64

Open
manucarrace opened this issue Jan 5, 2017 · 1 comment
Open

Missing x-auth-token header in Configure the south bound protocol #64

manucarrace opened this issue Jan 5, 2017 · 1 comment
Labels
bug

Comments

@manucarrace
Copy link
Collaborator

In http://fiware-iot-stack.readthedocs.io/en/release-v4.1/device_api/index.html#configure-the-south-bound-protocol there is no x-auth-token header.

I know this is not necesary from the point of view of the component, but from the pont of view of the platform or from the point of view of an integrator it would be nice to know that the x-auth-header is needed to provision a Configuration Group.
@manucarrace manucarrace changed the title Missing x-auth-token header Missing x-auth-token header in Configure the south boud protocol Jan 5, 2017
@manucarrace manucarrace changed the title Missing x-auth-token header in Configure the south boud protocol Missing x-auth-token header in Configure the south bound protocol Jan 5, 2017
@manucarrace manucarrace added the bug label Jan 5, 2017
@AlvaroVega
Copy link
Member

AFAIK iotagent is in charge of get token and use x-auth-token when device is configured with a trust id.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AlvaroVega @manucarrace