Hi Kuba,
Your quota for the user medbravouser has been increased up to 10 GB.
Regarding the errors you are experiencing through the API, please, send me in a private email your token (it is the only way, once I finish the tests you can generate a new one which will invalidate the current one) and I’ll check what is happening.
Best regards,
Francisco
De: Jakub Jurkiewicz <jakub at medbravo.org<mailto:jakub at medbravo.org>>
Fecha: miércoles, 13 de enero de 2016, 16:00
Para: Francisco Romero Bueno <francisco.romerobueno at telefonica.com<mailto:francisco.romerobueno at telefonica.com>>
CC: "fiware-tech-help at lists.fi-ware.org<mailto:fiware-tech-help at lists.fi-ware.org>" <fiware-tech-help at lists.fi-ware.org<mailto:fiware-tech-help at lists.fi-ware.org>>, Aurelia Bustos-Moreno <aurelia at medbravo.org<mailto:aurelia at medbravo.org>>
Asunto: Re: [FI-WARE-JIRA] (HELP-5555) [Fiware-fiche-coaching] How to connect existing cosmos user to FIWARE cloud authorization?
Hello Francisco,
I have finally manage to check that I succeded with option 2 - user: medbravouser on cosmos. SO please increase quota for this user.
However I have following issues.
kura at ckan2:/mnt/xmlCTAs$ curl -X GET "http://cosmos.lab.fiware.org:14000/webhdfs/v1/user/medbravouser?op=LISTSTATUS&user.name=medbravouser" -H "X-Auth-Token: xxxx"
curl: (56) Recv failure: Connection reset by peer
So I cannot list directory
kura at ckan2:/mnt/xmlCTAs$ curl -X GET "http://cosmos.lab.fiware.org:14000/webhdfs/v1/user/medbravouser?op=GETCONTENTSUMMARY&user.name=medbravouser" -H "X-Auth-Token: xxxx"
curl: (56) Recv failure: Connection reset by peer
the same
kura at ckan2:/mnt/xmlCTAs$ curl -X GET "http://cosmos.lab.fiware.org:14000/webhdfs/v1/user/medbravouser/tagged.sf?op=OPEN&user.name=medbravouser" -H "X-Auth-Token: xxxx" > tagged.sf
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 274 100 274 0 0 33 0 0:00:08 0:00:08 --:--:-- 68
kura at ckan2:/mnt/xmlCTAs$ less tagged.sf Error: Parse Error at Error (native)
at Socket.socketOnData (_http_client.js:317:20)
at Socket.emit (events.js:107:17)
at readableAddChunk (_stream_readable.js:163:16)
at Socket.Readable.push (_stream_readable.js:126:10)
at TCP.onread (net.js:538:20)
So getting file /user/medbravouser/tagged.sf fails.
But with the same auth token
curl -X GET "http://cosmos.lab.fiware.org:14000/webhdfs/v1/user/medbravouser/ala?op=OPEN&user.name=medbravouser" -H "X-Auth-Token: xxx"
returns:
ala alal alla
which is content of 1/user/medbravouser/ala.
Can you check my errors? And I am waiting for bigger quota.
Best,
Kuba
On Mon, Jan 11, 2016 at 10:05 AM, FRANCISCO ROMERO BUENO <francisco.romerobueno at telefonica.com<mailto:francisco.romerobueno at telefonica.com>> wrote:
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 at medbravo.org<mailto:fiware at 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 at medbravo.org<mailto:fiware at 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 at medbravo.org<mailto:medbravouser at 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 at fi-ware.org<mailto:jira-help-desk at 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 at medbravo.org<mailto:fiware at 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 at medbravo.org<mailto:fiware at 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<http://www.medbravo.org>
>> Since January 1st, old domains won't be supported and messages sent to
>>any domain different to @lists.fiware.org<http://lists.fiware.org> will be lost.
>> Please, send your messages using the new domain
>>(Fiware-fiche-coaching at lists.fiware.org<mailto:Fiware-fiche-coaching at lists.fiware.org>) instead of the old one.
>> _______________________________________________
>> Fiware-fiche-coaching mailing list
>> Fiware-fiche-coaching at lists.fiware.org<mailto:Fiware-fiche-coaching at lists.fiware.org>
>> https://lists.fiware.org/listinfo/fiware-fiche-coaching
>> [Created via e-mail received from: Jakub Jurkiewicz
>><jakub at medbravo.org<mailto:jakub at 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
--
[https://docs.google.com/uc?export=download&id=0B8O55AP05MC-ZElISjhjR0dxcGs&revid=0B8O55AP05MC-anc4NUh0bktCcGwzaTRObWNTZ2hvTlNneEtBPQ]<tel:%2B34%20618%2045%2032%2014>
Jakub Jurkiewicz, Ph.D
FIWARE Data Scientist
www.medbravo.org<http://www.medbravo.org/>
________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-tech-help/attachments/20160114/f09292ae/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy