Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Component/s: Finish
-
Labels:None
-
Sender Email:
-
External Participants:
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@atb-bremen.de finish-technology-bounces@atb-bremen.de Im Auftrag von Robin Puthli
Gesendet: Dienstag, 5. Juli 2016 15:04
An: FInish-technology@finish-project.eu
Cc: Cor Verdouw <cor.verdouw@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.
[cid:image001.png@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@itude.com<r.puthli@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**
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@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-finish-coaching mailing list
Fiware-finish-coaching@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-finish-coaching
[Created via e-mail received from: Peter Einramhof <einramhof@atb-bremen.de>]
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