Details
-
Type: Monitor
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
HD-Chapter:Security
-
HD-Enabler:KeyRock
Description
Created question in FIWARE Q/A platform on 10-03-2016 at 18:03
Please, ANSWER this question AT https://ask.fiware.org/question/427/keyrock-and-spring-security/
Question:
Keyrock and Spring Security
Description:
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.
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. :/
Activity
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
3d 14h 6m | 1 | Alvaro Alonso | 14/Mar/16 9:08 AM | |||||
|
1s | 1 | Alvaro Alonso | 14/Mar/16 9:08 AM | |||||
|
1s | 1 | Alvaro Alonso | 14/Mar/16 9:08 AM |
Fix Version/s | 2021 [ 12600 ] |
Summary | FIWARE.Question.Tech.Keyrock and Spring Security | FIWARE.Question.Tech.Security.IDM-KeyRock.Keyrock and Spring Security |
HD-Chapter | Security [ 10841 ] |
HD-Enabler | KeyRock [ 10889 ] | |
Description |
Created question in FIWARE Q/A platform on 10-03-2016 at 18:03 {color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/427/keyrock-and-spring-security/ +Question:+ Keyrock and Spring Security +Description:+ 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. :/ |
Created question in FIWARE Q/A platform on 10-03-2016 at 18:03 {color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/427/keyrock-and-spring-security/ +Question:+ Keyrock and Spring Security +Description:+ 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. :/ |
Summary | [fiware-askbot] Keyrock and Spring Security | FIWARE.Question.Tech.Keyrock and Spring Security |
Resolution | Done [ 10000 ] | |
Status | Answered [ 10104 ] | Closed [ 6 ] |
Status | In Progress [ 3 ] | Answered [ 10104 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Assignee | Alvaro Alonso [ aalonsog ] |
Field | Original Value | New Value |
---|---|---|
Component/s | FIWARE-TECH-HELP [ 10278 ] |
2016-03-10 19:05|CREATED monitor | # answers= 0, accepted answer= False