Hi Kuba,

If I¹ve understood well, the problem is your FIWARE Lab credentials (the
ones you use for retrieving the OAuth2 token) are not linked to your
Cosmos user. I.e. your FIWARE Lab credentials are based on the
"fiware@medbravo.org" email, and the Cosmos account is ³medbravouser²; in
that case, you are right, the authentication will fail since the
authentication mechanism (1) will take the token and will retrieve the
"fiware@medbravo.org" email, and (2) then the ³fiware" Cosmos account
(i.e. the substring until the Œ@Œ)  will be involved in the authorization.

I guess this is happening because the medbravouser account was created at
the very begining of the project, when no provisioning portal was
available. In this case, there are two options:

* If you control the ³fiware² user then all the data could be moved there
from the ³medbravo² account. Then the ³fiware² account will start working
with OAuth2.
* You can register a new email in FIWARE Lab, let¹s say
³medbravouser@medbravo.org², and the ³medbravouser² account will start
working with OAuth2.

The second one option is the preferred for me.

In addition, since you requested an increment of the quota, I¹ll wait
until you tell me which Cosmos account will finally be used.

Regards,
Francisco

El 7/1/16 9:41, "Franck Le Gall (JIRA)" <jira-help-desk@fi-ware.org>
escribió:

>
>    [
>https://jira.fiware.org/browse/HELP-5555?page=com.atlassian.jira.plugin.sy
>stem.issuetabpanels:comment-tabpanel&focusedCommentId=38888#comment-38888
>]
>
>Franck Le Gall commented on HELP-5555:
>--------------------------------------
>
>Hello Francisco,
>
>Do you have answers for that company ?
>
>Many thanks
>Franck
>
>
>> [Fiware-fiche-coaching] How to connect existing cosmos user to FIWARE
>>cloud authorization?
>>
>>-------------------------------------------------------------------------
>>-----------------
>>
>>                 Key: HELP-5555
>>                 URL: https://jira.fiware.org/browse/HELP-5555
>>             Project: Help-Desk
>>          Issue Type: extRequest
>>          Components: FIWARE-TECH-HELP
>>            Reporter: FW External User
>>            Assignee: Francisco Romero
>>
>> Hello,
>>    Medbravo has use medbravouser on cosmos default instance. We also has
>> user fiware@medbravo.org on fiware cloud.
>> To enable http access I need OATH2 token - which is granted only from
>> cosmos cloud. Is it possible to to allow authorization for medbravouser
>>to
>> be made from account fiware@medbravo.org? Or should I use on cosmos
>>account
>> fiware? ( I have already reported that I get access to that account).
>>     Best,
>>       Kuba
>> --
>> <%2B34%20618%2045%2032%2014>
>>      Jakub Jurkiewicz, Ph.D
>>      FIWARE Data Scientist
>>      www.medbravo.org
>> Since January 1st, old domains won't be supported and messages sent to
>>any domain different to @lists.fiware.org will be lost.
>> Please, send your messages using the new domain
>>(Fiware-fiche-coaching@lists.fiware.org) instead of the old one.
>> _______________________________________________
>> Fiware-fiche-coaching mailing list
>> Fiware-fiche-coaching@lists.fiware.org
>> https://lists.fiware.org/listinfo/fiware-fiche-coaching
>> [Created via e-mail received from: Jakub Jurkiewicz
>><jakub@medbravo.org>]
>
>
>
>--
>This message was sent by Atlassian JIRA
>(v6.4.1#64016)


________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição