Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Component/s: FI-C3
-
Labels:None
Description
Dear Franck,
Introducing myself first of all I am supervising the software development
and would like to touch base with you
Referring to our virtual meeting last Tuesday:
Having implemented FiWare key-rock-identity management in VeloCarrier’s
Portal we would like to discuss two aspects :
First according to our delivery plan we thought that implementation of one
Fiware enabler / tools at this point in time
Is sufficient and meets your expectations. Having seen your reaction we just
were a bit surprised. From a software point
Of view we could integrate other enablers if it makes sense from a processs
point of view for VeloCarrier.
Second we have Implemented IDM keyrock management in the web portal
which after authentication will be redirected to our Velo Carrier
application page.
Everything works fine but we have a technical difficulty. The logout
functionality does not seem to work in the way as expected.
When someone logs out as a franchise owner the session does not terminate
properly. And when I login as a Franchise owner again I am automatically
logged in with old credentials.
In short the IDM keyrock management session is not terminated properly and
to login as a franchise owner we have to clear cache manually
(ctrl+shift+del) each time in the browser.
Could you please share your thoughts and insights with regards to this issue
and how to overcome this?
Expecting your kind reply.
Rudolf Weiss
Development
FaRa Logistic Consult GmbH
Am Stadtgraben 19
72070 Tübingen
Telefon 0 70 71 / 145 00 00
Telefax 0 70 71 / 145 00 09
www.velocarrier.de
info@velocarrier.de
Amtsgericht Stuttgart HRB 354482
Geschäftsführer:
Raimund Rassillier, Torsten Fauser
Umsatzsteuer-ID: DE240914144
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-fic3-coaching@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-fic3-coaching mailing list
Fiware-fic3-coaching@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-fic3-coaching
[Created via e-mail received from: Velocarrier <r.weiss@velocarrier.de>]
The issue has been emailed:
HELC-1230) [Fiware-fic3-coaching] VeloCarrier *Dear Rudolf
I confirm I have been disappointed by the presentation.
First, the FI-C3 calls was clearly mentioning that applications should make use of at least 2, ideally connected enablers.
But my main disappointment is that you selected one enabler which does not really brings you the FIWARE added value and I question your choice as other 3rd party system exist which may have better fit your needs.
So my recommendation is to look at enablers really having added value to you and as discussed, building your back-end system on top of the FIWARE context information management paradigm would really make sense.
The kind of application your are building is going to have several components generating events (parcel is pick-up, parcel is delivered, etc.) and other which would like to subscribe to these events (micro-service model). This is exactly the FIWARE model.
So rather than trying to build you own backend on LAMP, I strongly encourage you to start at the functionalities offered by the context broker (http://catalogue.fiware.org/enablers/publishsubscribe-context-broker-orion-context-broker)
From that point, you will then be able to expand toward other functionalities including Complex Events Processnig, Analytics ,etc.
We can set-up a call to further discuss this
Franck