[Fiware-tech-help] FW: [Saf2-techteam] [documentation] Few technical questions (#9)

[Raul Palma]

Dear fiware tech team,
We have received the question below from one of the SMEs of SmartAgriFood2
accelerator.
Could you help us to answer his question?
Thanks,
Raul

From:  maticserc <notifications at github.com>
Reply-To:  SAF2/documentation
<reply+00ab6986ad5d2078c46a05f5bad253b94b5529415f59084892cf00000001114612ed9
2a169ce0400473a at reply.github.com>
Date:  Wednesday 15 April 2015 13:52
To:  SAF2/documentation <documentation at noreply.github.com>
Subject:  Re: [Saf2-techteam] [documentation] Few technical questions (#9)


Hi Jan Willem and maybe somebody else may help; I have one more question.

We are using FIWARE Lab's instance of OAuth2. We have the following problem:
assuming that {TOKEN} is an actual user's token (a long cryptic string).

1) log-in works well, our callback is called with the ?code={TOKEN}
parameter from FIware
2) if we use this token to access the user data with the URL
http://account.lab.fi-ware.org/user?access_token={TOKEN}
<http://account.lab.fi-ware.org/user?access_token=%7BTOKEN%7D> , we get the
following message:
{"error":"invalid_token","error_description":"The access token provided is
expired, revoked, malformed or invalid for other reasons."}

even though we don't log out or do anything between the log-in and the step
"2)".

My other question would be whether we may use the methods, described under
http://developer.openstack.org/api-ref-identity-v3.html with FIWARE Lab's
authentication system, and if yes, then what to append in front of the URL
calls.

Optionally: do the same concepts apply to FIspace's authentication system?

Best,
Matic

‹
Reply to this email directly or view it on GitHub
<https://github.com/SAF2/documentation/issues/9#issuecomment-93349357> .

 
   
 
_______________________________________________ SAF2-TECHTEAM mailing list
SAF2-TECHTEAM at lists.man.poznan.pl
https://lists.man.poznan.pl/mailman/listinfo/saf2-techteam

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20150416/b41a6d67/attachment.html>