Revision history [back]

Hi all,

I'm writing an API provider in Java Spring to orchestrate some Fiware GE APIs. I registered an application against my org in the Lab and - having read a bunch of tutorials, manuals, etc... - I was expecting everything to work, except it doesn't. :D

Basically Spring seems to be calling the URI https://account.lab.fiware.org/user withouth encoding the access_token - I suspect it's using an Authorization header with "bearer token" format.

Does anyone know what magic incantation is necessary to persuade Spring to append the token parameter? All I found online appears to assume that the User Info URI is always called as-is. :/

Hi all,

I'm writing an API provider in Java Spring to orchestrate some Fiware GE APIs. I registered an application against my org in the Lab and - having read a bunch of tutorials, manuals, etc... - I was expecting everything to work, except it doesn't. :D

Basically Spring seems to be calling the URI https://account.lab.fiware.org/user withouth encoding the access_token - I suspect it's using an Authorization header with "bearer token" format.

Does anyone know what magic incantation is necessary to persuade Spring to append the token parameter? All I found online appears to assume that the User Info URI is always called as-is. :/

Hi all,

I'm writing an API provider in Java Spring to orchestrate some Fiware GE APIs. I registered an application against my org in the Lab and - having read a bunch of tutorials, manuals, etc... - I was expecting everything to work, except it doesn't. :D

Basically Spring seems to be calling the URI https://account.lab.fiware.org/user withouth encoding the access_token - I suspect it's using an Authorization header with "bearer token" format.

Does anyone know what magic incantation is necessary to persuade Spring to append the token parameter? All I found online appears to assume that the User Info URI is always called as-is. :/