From einramhof at atb-bremen.de Tue Jul 5 15:43:35 2016 From: einramhof at atb-bremen.de (Peter Einramhof) Date: Tue, 5 Jul 2016 13:43:35 +0000 Subject: [Fiware-finish-coaching] WG: [FInish-Technology] KeyRock status after FINISH ends In-Reply-To: References: Message-ID: <7E9CA4F5F44F4C48B57A840A6184630D5613F5E0@kenny> 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 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. [cid:image001.png at 01D1D6D3.ACEDBC80] 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 [cid:DBE2B82F-A4DD-42A8-8906-E4CEBC37BAC6] 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 ? google.com/+RobinPuthli ? skype: robin.puthli ? linkedIn:nl.linkedin.com/in/puthli/ www.itude.com ? K.v.K. 30146090 _____________________________________________________________________________ ***Op deze mail is een disclaimer van toepassing. De inhoud daarvan is te lezen op onze website*** -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-2.png Type: image/png Size: 3935 bytes Desc: PastedGraphic-2.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 24940 bytes Desc: image001.png URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From omer.ozdemir at atos.net Thu Jul 7 13:52:00 2016 From: omer.ozdemir at atos.net (Ozdemir, Omer Faruk) Date: Thu, 7 Jul 2016 11:52:00 +0000 Subject: [Fiware-finish-coaching] WG: [FInish-Technology] KeyRock status after FINISH ends In-Reply-To: <7E9CA4F5F44F4C48B57A840A6184630D5613F5E0@kenny> References: , <7E9CA4F5F44F4C48B57A840A6184630D5613F5E0@kenny> Message-ID: 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 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 ? google.com/+RobinPuthli ? skype: robin.puthli ? linkedIn:nl.linkedin.com/in/puthli/ 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: From coaches-help-desk-jira at fi-ware.org Thu Jul 7 13:55:00 2016 From: coaches-help-desk-jira at fi-ware.org (Help-Coaches-Desk) Date: Thu, 7 Jul 2016 12:55:00 +0100 (BST) Subject: [Fiware-finish-coaching] [FIWARE-JIRA] (HELC-1430) WG: [FInish-Technology] KeyRock status after FINISH ends In-Reply-To: References: Message-ID: >From FIWARE JIRA - Coaches Help Desk ---- ------------------------------------------------------------------------------- Comments: Ozdemir, Omer Faruk - Today 1:54 PM ------------------ 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 ------------------------ Issue id: HELC-1430 Description: 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 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. [cid:image001.png at 01D1D6D3.ACEDBC80] 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 [cid:DBE2B82F-A4DD-42A8-8906-E4CEBC37BAC6] 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 ? google.com/+RobinPuthli ? skype: robin.puthli ? linkedIn:nl.linkedin.com/in/puthli/ www.itude.com ? K.v.K. 30146090 _____________________________________________________________________________ ***Op deze mail is een disclaimer van toepassing. De inhoud daarvan is te lezen op onze website*** 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-finish-coaching at lists.fiware.org) instead of the old one. _______________________________________________ Fiware-finish-coaching mailing list Fiware-finish-coaching at lists.fiware.org https://lists.fiware.org/listinfo/fiware-finish-coaching [Created via e-mail received from: Peter Einramhof ] FIWARE Chapter: FIWARE GEri: Status: Open --------------------- This email was generated by FIWARE JIRA following an email received into the Coaches Help Desk. From omer.ozdemir at atos.net Thu Jul 14 09:56:39 2016 From: omer.ozdemir at atos.net (Ozdemir, Omer Faruk) Date: Thu, 14 Jul 2016 07:56:39 +0000 Subject: [Fiware-finish-coaching] WG: [FInish-Technology] KeyRock status after FINISH ends In-Reply-To: References: , <7E9CA4F5F44F4C48B57A840A6184630D5613F5E0@kenny>, Message-ID: Dear Peter, good morning, I've contacted with Alvaro Alonso and he said that they are already working on this issue, you will hear from them in a short time hopefully. Kind regards Omer ________________________________ From: Ozdemir, Omer Faruk Sent: Thursday, July 07, 2016 2:52 PM To: Peter Einramhof; Chulani, Ilknur Cc: Fiware-finish-coaching at lists.fiware.org; Robin Puthli (r.puthli at itude.com); Karaboga, Burak Subject: RE: [Fiware-finish-coaching] WG: [FInish-Technology] KeyRock status after FINISH ends 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 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. [X] 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 [X] 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 ? google.com/+RobinPuthli ? skype: robin.puthli ? linkedIn:nl.linkedin.com/in/puthli/ 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: From coaches-help-desk-jira at fi-ware.org Thu Jul 14 10:00:00 2016 From: coaches-help-desk-jira at fi-ware.org (Help-Coaches-Desk) Date: Thu, 14 Jul 2016 09:00:00 +0100 (BST) Subject: [Fiware-finish-coaching] [FIWARE-JIRA] (HELC-1430) WG: [FInish-Technology] KeyRock status after FINISH ends In-Reply-To: References: Message-ID: >From FIWARE JIRA - Coaches Help Desk ---- ------------------------------------------------------------------------------- Comments: Ozdemir, Omer Faruk - Today 9:59 AM ------------------ Dear Peter, good morning, I've contacted with Alvaro Alonso and he said that they are already working on this issue, you will hear from them in a short time hopefully. Kind regards Omer Ozdemir, Omer Faruk - 07/Jul/16 1:54 PM ------------------ 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 ------------------------ Issue id: HELC-1430 Description: 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 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. [cid:image001.png at 01D1D6D3.ACEDBC80] 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 [cid:DBE2B82F-A4DD-42A8-8906-E4CEBC37BAC6] 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 ? google.com/+RobinPuthli ? skype: robin.puthli ? linkedIn:nl.linkedin.com/in/puthli/ www.itude.com ? K.v.K. 30146090 _____________________________________________________________________________ ***Op deze mail is een disclaimer van toepassing. De inhoud daarvan is te lezen op onze website*** 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-finish-coaching at lists.fiware.org) instead of the old one. _______________________________________________ Fiware-finish-coaching mailing list Fiware-finish-coaching at lists.fiware.org https://lists.fiware.org/listinfo/fiware-finish-coaching [Created via e-mail received from: Peter Einramhof ] FIWARE Chapter: FIWARE GEri: Status: Open --------------------- This email was generated by FIWARE JIRA following an email received into the Coaches Help Desk. From einramhof at atb-bremen.de Thu Jul 14 10:09:31 2016 From: einramhof at atb-bremen.de (Peter Einramhof) Date: Thu, 14 Jul 2016 08:09:31 +0000 Subject: [Fiware-finish-coaching] WG: [FInish-Technology] KeyRock status after FINISH ends In-Reply-To: References: , <7E9CA4F5F44F4C48B57A840A6184630D5613F5E0@kenny>, Message-ID: <7E9CA4F5F44F4C48B57A840A6184630D5615F368@kenny> Dear Omer, dear Alvaro, thanks a lot for taking care of this issue! Very much appreciated. Kind regards, Peter. Von: Ozdemir, Omer Faruk [mailto:omer.ozdemir at atos.net] Gesendet: Donnerstag, 14. Juli 2016 09:57 An: Peter Einramhof ; Chulani, Ilknur Cc: Fiware-finish-coaching at lists.fiware.org; Robin Puthli (r.puthli at itude.com) ; Karaboga, Burak ; ?lvaro Alonso Betreff: RE: [Fiware-finish-coaching] WG: [FInish-Technology] KeyRock status after FINISH ends Dear Peter, good morning, I've contacted with Alvaro Alonso and he said that they are already working on this issue, you will hear from them in a short time hopefully. Kind regards Omer ________________________________ From: Ozdemir, Omer Faruk Sent: Thursday, July 07, 2016 2:52 PM To: Peter Einramhof; Chulani, Ilknur Cc: Fiware-finish-coaching at lists.fiware.org; Robin Puthli (r.puthli at itude.com); Karaboga, Burak Subject: RE: [Fiware-finish-coaching] WG: [FInish-Technology] KeyRock status after FINISH ends 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 > 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. 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 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 ? google.com/+RobinPuthli ? skype: robin.puthli ? linkedIn:nl.linkedin.com/in/puthli/ 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: From coaches-help-desk-jira at fi-ware.org Thu Jul 14 10:12:00 2016 From: coaches-help-desk-jira at fi-ware.org (Help-Coaches-Desk) Date: Thu, 14 Jul 2016 09:12:00 +0100 (BST) Subject: [Fiware-finish-coaching] [FIWARE-JIRA] (HELC-1430) WG: [FInish-Technology] KeyRock status after FINISH ends In-Reply-To: References: Message-ID: >From FIWARE JIRA - Coaches Help Desk ---- ------------------------------------------------------------------------------- Comments: FW External User - Today 10:11 AM ------------------ Comment by einramhof at atb-bremen.de : Dear Omer, dear Alvaro, thanks a lot for taking care of this issue! Very much appreciated. Kind regards, Peter. Von: Ozdemir, Omer Faruk [mailto:omer.ozdemir at atos.net] Gesendet: Donnerstag, 14. Juli 2016 09:57 An: Peter Einramhof ; Chulani, Ilknur Cc: Fiware-finish-coaching at lists.fiware.org; Robin Puthli (r.puthli at itude.com) ; Karaboga, Burak ; ?lvaro Alonso Betreff: RE: [Fiware-finish-coaching] WG: [FInish-Technology] KeyRock status after FINISH ends Dear Peter, good morning, I've contacted with Alvaro Alonso and he said that they are already working on this issue, you will hear from them in a short time hopefully. Kind regards Omer Ozdemir, Omer Faruk - Today 9:59 AM ------------------ Dear Peter, good morning, I've contacted with Alvaro Alonso and he said that they are already working on this issue, you will hear from them in a short time hopefully. Kind regards Omer Ozdemir, Omer Faruk - 07/Jul/16 1:54 PM ------------------ 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 ------------------------ Issue id: HELC-1430 Description: 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 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. [cid:image001.png at 01D1D6D3.ACEDBC80] 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 [cid:DBE2B82F-A4DD-42A8-8906-E4CEBC37BAC6] 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 ? google.com/+RobinPuthli ? skype: robin.puthli ? linkedIn:nl.linkedin.com/in/puthli/ www.itude.com ? K.v.K. 30146090 _____________________________________________________________________________ ***Op deze mail is een disclaimer van toepassing. De inhoud daarvan is te lezen op onze website*** 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-finish-coaching at lists.fiware.org) instead of the old one. _______________________________________________ Fiware-finish-coaching mailing list Fiware-finish-coaching at lists.fiware.org https://lists.fiware.org/listinfo/fiware-finish-coaching [Created via e-mail received from: Peter Einramhof ] FIWARE Chapter: FIWARE GEri: Status: Open --------------------- This email was generated by FIWARE JIRA following an email received into the Coaches Help Desk. From coaches-help-desk-jira at fi-ware.org Wed Jul 27 14:41:00 2016 From: coaches-help-desk-jira at fi-ware.org (Help-Coaches-Desk) Date: Wed, 27 Jul 2016 13:41:00 +0100 (BST) Subject: [Fiware-finish-coaching] [FIWARE-JIRA] (HELC-1430) WG: [FInish-Technology] KeyRock status after FINISH ends In-Reply-To: References: Message-ID: >From FIWARE JIRA - Coaches Help Desk ---- ------------------------------------------------------------------------------- Comments: ilknur chulani - Today 3:40 PM ------------------ Dear Peter and Robin, Federico Alvarez has responded to your question in the Stackoverflow posting. Does it solve your problem: https://stackoverflow.com/questions/37094473/fiware-keyrock-scim-api-bug-check-allowed-to-get-and-assign-got-an-unexpecte Best regards, ilknur FW External User - 14/Jul/16 11:11 AM ------------------ Comment by einramhof at atb-bremen.de : Dear Omer, dear Alvaro, thanks a lot for taking care of this issue! Very much appreciated. Kind regards, Peter. Von: Ozdemir, Omer Faruk [mailto:omer.ozdemir at atos.net] Gesendet: Donnerstag, 14. Juli 2016 09:57 An: Peter Einramhof ; Chulani, Ilknur Cc: Fiware-finish-coaching at lists.fiware.org; Robin Puthli (r.puthli at itude.com) ; Karaboga, Burak ; ?lvaro Alonso Betreff: RE: [Fiware-finish-coaching] WG: [FInish-Technology] KeyRock status after FINISH ends Dear Peter, good morning, I've contacted with Alvaro Alonso and he said that they are already working on this issue, you will hear from them in a short time hopefully. Kind regards Omer Ozdemir, Omer Faruk - 14/Jul/16 10:59 AM ------------------ Dear Peter, good morning, I've contacted with Alvaro Alonso and he said that they are already working on this issue, you will hear from them in a short time hopefully. Kind regards Omer Ozdemir, Omer Faruk - 07/Jul/16 2:54 PM ------------------ 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 ------------------------ Issue id: HELC-1430 Description: 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 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. [cid:image001.png at 01D1D6D3.ACEDBC80] 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 [cid:DBE2B82F-A4DD-42A8-8906-E4CEBC37BAC6] 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 ? google.com/+RobinPuthli ? skype: robin.puthli ? linkedIn:nl.linkedin.com/in/puthli/ www.itude.com ? K.v.K. 30146090 _____________________________________________________________________________ ***Op deze mail is een disclaimer van toepassing. De inhoud daarvan is te lezen op onze website*** 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-finish-coaching at lists.fiware.org) instead of the old one. _______________________________________________ Fiware-finish-coaching mailing list Fiware-finish-coaching at lists.fiware.org https://lists.fiware.org/listinfo/fiware-finish-coaching [Created via e-mail received from: Peter Einramhof ] FIWARE Chapter: FIWARE GEri: Status: Open --------------------- This email was generated by FIWARE JIRA following an email received into the Coaches Help Desk.