[Fiware-finish-coaching] WG: [FInish-Technology] KeyRock status after FINISH ends

Ozdemir, Omer Faruk omer.ozdemir at atos.net
Thu Jul 7 13:52:00 CEST 2016


Dear Peter,

Ilknur is now on holidays, me and my collegue Burak are here to help you.

Could you please share the Jira ticket number/link(if there has been created once before)?
Or there is only stackoverflow page for this issue?

We will take necessary actions one you share the details with us..

Kind regards
Omer
________________________________
From: fiware-finish-coaching-bounces at lists.fiware.org [fiware-finish-coaching-bounces at lists.fiware.org] on behalf of Peter Einramhof [einramhof at atb-bremen.de]
Sent: Tuesday, July 05, 2016 4:43 PM
To: Chulani, Ilknur
Cc: Fiware-finish-coaching at lists.fiware.org; Robin Puthli (r.puthli at itude.com)
Subject: [Fiware-finish-coaching] WG: [FInish-Technology] KeyRock status after FINISH ends

Dear Ilknur,

one of our teams had reported an issue with KeyRock some months ago – while there had been some contact
with the developer(s) of the GE, and the response that they are working on it (May 23rd), there hasn’t been any
progress/solution of this issue until today – see email below.

Is there a way to boost the priority of the issue and get the seemingly stopped wheels in motion again?

Kind regards,
Peter on behalf of FInish.



Von: finish-technology-bounces at atb-bremen.de [mailto:finish-technology-bounces at atb-bremen.de] Im Auftrag von Robin Puthli
Gesendet: Dienstag, 5. Juli 2016 15:04
An: FInish-technology at finish-project.eu
Cc: Cor Verdouw <cor.verdouw at wur.nl>
Betreff: [FInish-Technology] KeyRock status after FINISH ends

Dear FINISH technology readers,

I am increasingly concerned about the KeyRock Generic Enabler.
We have an outstanding issue which was not essential for our FINISH project, but which will block future development:
https://stackoverflow.com/questions/37094473/fiware-keyrock-scim-api-bug-check-allowed-to-get-and-assign-got-an-unexpecte

The issue has been open for two months and the developer does not seem interested in fixing it. The code on Github seems to have come to a complete halt after May 2016.
[UrlBlockedError.aspx]

I have spoken to a bunch of FIWARE projects and have not met one that has adopted KeyRock on their own infrastructure. So i am hoping that we are not the only company using it?
At the present rate of maintenance on the KeyRock IDM we will likely be forced to abandon it and substitute with a different identity management product or write our own. Neither options are very attractive.

Is there anything you can do to bump this issue up in priority?
Is there anything you can do to salvage this GE, which otherwise seems doomed?

Best regards,
Robin Puthli


Met vriendelijke groet,

Robin Puthli
Directeur


[UrlBlockedError.aspx]
Lageweg 2
3703 CA Zeist
■ mob +31(0) 6 21 88 22 86
■ tel direct +31(0)30 692 60 04
■ tel receptie +31(0)30 699 70 20
■ mail r.puthli at itude.com<mailto:r.puthli at itude.com>
■ google.com/+RobinPuthli<http://google.com/+RobinPuthli>
■ skype: robin.puthli
■ linkedIn:nl.linkedin.com/in/puthli/<http://nl.linkedin.com/in/puthli/>


www.itude.com<http://www.itude.com/> ■ K.v.K. 30146090
_____________________________________________________________________________
***Op deze mail is een disclaimer van toepassing. De inhoud daarvan is te lezen op onze website***


ATOS WARNING !
This message contains attachments that could potentially harm your computer.
Please make sure you open ONLY attachments from senders you know, trust and is in an e-mail that you are expecting.

AVERTISSEMENT ATOS !
Ce message contient des pièces jointes qui peuvent potentiellement endommager votre ordinateur.
Merci de vous assurer que vous ouvrez uniquement les pièces jointes provenant d’emails que vous attendez et dont vous connaissez les expéditeurs et leur faites confiance.

AVISO DE ATOS !
Este mensaje contiene datos adjuntos que pudiera ser que dañaran su ordenador.
Asegúrese de abrir SOLO datos adjuntos enviados desde remitentes de confianza y que procedan de un correo esperado.

ATOS WARNUNG !
Diese E-Mail enthält Anlagen, welche möglicherweise ihren Computer beschädigen könnten.
Bitte beachten Sie, daß Sie NUR Anlagen öffnen, von einem Absender den Sie kennen, vertrauen und vom dem Sie vor allem auch E-Mails mit Anlagen erwarten.
Bu mesaj ve ekleri gönderilen kişiye özeldir ve gizli bilgiler içerebilir. Eğer mesajın gönderilmek istendiği kişi değilseniz lütfen kopyalamayınız, başkalarına göndermeyiniz ve göndericiyi bilgilendiriniz. Internet üzerinden gönderilen mesajların güvenli ve hatasız olduğunun garantisi olmadığından Atos grubu mesajın içeriğinden sorumlu tutulamaz. Göndericinin bilgisayarı anti-virüs sistemleri tarafından taranmaktadır, ancak yine de mesajın virüs içermediği garanti edilemez ve gönderici, meydana gelebilecek zararlardan sorumlu tutulamaz.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-finish-coaching/attachments/20160707/e696a46d/attachment.html>


More information about the Fiware-finish-coaching mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy