Main thread: External Data Server Proof-Of-Concept - Work Breakdown Structure
Next Meeting - (regular) VHAL / Vehicle Data APIs weekly call - Tuesday 19 May 2 June - 17:00-18:00 CET
Dial by your location: find your local number here
Agenda
- GENIVI Virtual Technical Summit Workshop - Debrief and next stepsbacklog review
- AOB
Backlog
| Expand |
|---|
Backlog
|
...
- Alex: we are using Apollo graphql server which needs an addition for web token management, and other stuff we are working on, I have discussed which contribution we could do with Markus
- BMW has the blue box on the right box (authentication) (look at the EDS architecture diagram)
- BMW has only the EDS implementation, not the Internal Data Server one
- Alex: the permissions are not yet what we need
- discussion on the work to do for the authentication and the access control groups
- Gunnar: we need to do a more formal description of things to be done for the authentication
- Alex: might be able to do some work in the next days, will try out my ideas on an actual implementation, as soon as I have something (next week possibly), I will generate some docs like ppt
- Alex: tooling is not clear for me yet, as soon as we agree on the way to specify things, we will talk about tooling and manifest generation
- discussion on the naming of artefacts
- Alex: we want to have a nodeJS graphql implementation running
- Alex: I can describe the nodeJS and graphql installation and the deployment of json files
- Gunnar: the wiki page for documenting tihs is AASIG: Implementation notes
- /TODO/ Alex to describe the nodeJS and graphql installation in the above wiki page
- Stefan: at Alex, since you have the authentication implementation under way, could you spent some time to describe what you have done so that we can identify the leftovers ?
- Alex: I can explain that, for instance we need a json web token implementation
- /TODO/ Alex & Stefan to clarify what could be the contribution of BMW & Tieto to the authentication mechanism implementation
...