Dear FIWARE coach,
we forward you a support request received from a CreatiFI applicant we are
not able to solve.
Please let us know if you need direct contact with the submitter.
Thanks.

*****************************

Hi, we're having a bit of an issue with KeyRock authentication.

To be able to integrate VBOT platform with KeyRock (and other identity
providers), we've built a federated authorisation system, based around
OAuth2. At the moment as it stands you can login to VBOT platform using
many different identity providers, including Facebook or Twitter for
example. The same way, we wanted to include an option to sign in with
KeyRock based account - in this case a FIware account.

Are there any differences in the way KeyRock server would authorise users,
vs a standard oauth2 server (ie - according to the oauth2 specification
http://tools.ietf.org/html/rfc6749)?
Could you please let us know if there are any additional headers, requests
or variations required for the KeyRock server to work the way as we
intended?

We are trying to use our oauth2 client to connect to KeyRock or FIWARE
accounts but unfortunately, it didnt work.

We also tried using omniauth-fiware gem in our rails app but it didn't work
either - in callback phase, we're getting:

ERROR – omniauth: (fiware) Authentication failure!
invalid_credentials: OAuth2::Error, Authentication header missing. Use
HTTP Basic.

*****************************

_______________________________________________
Fiware-creatifi-coaching mailing list
Fiware-creatifi-coaching@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-creatifi-coaching

[Created via e-mail received from: Andrea Maestrini <amaestrini@create-net.org>]