Page History

...

Agenda

• TietoEVRY short demo
• authentication implementation (work sharing between BMW & TietoEVRY)
• graphql and nodeJS installation
• staffing the EDS PoC
• PoC planning
• AOB

• Backlog

  Expand

  Backlog Android Compatibility Definition Document Software architectural task force : Vehicle Data architecture for Android Comparison of how vehicle properties are managed by Android 9 and 10 (Q) - further inputs question to address in the group: what do participating companies intend to do with the JAPI (Java API similar to CommonAPI for Android) ? this building block is currently missing Signal to service translation Secure access control in Some/IP

External Data Server Proof-Of-Concept - Work Breakdown Structure

Friday 27 March March - 200pm CET

Participants

• Alex, Stefan, Philippe

Agenda

• authentication service implementation (work sharing between BMW & TietoEVRY)
• AOB

Minutes

1. BMW has implemented the Service for Authentication:

• Service written in Kotlin - conclusion: Android buildsystem does not support Kotlin yet - needs to be rewritten if integrated in platform
• IPC between Service - App done manually - conclusion: can be rewritten to hide boilerplate via AIDL generators
• JWT kept internally as string with payload: uid + permissions as a List<String>
• Secretkey to sign JWT shared manually (i.e. no single point of encrypted storage) - Action to be put in the backlog: "Decide and configure storage of secret between Server and Clients")
• Example permissions exposed in AndroidManifest

2. BWM has implemented the Client application to use Authentication Service:

• JWT retrieved as bundle - can be reworked for AIDL object
• Connection to GraphQL not analyzed, but not that relevant for the scope of Authentication Service

3. The code is not shared yet because of process of licensing and OSS check by BMW

4. We had a little session about finding similarities/improvements/possible reusage of https://github.com/GENIVI/aasig_dev_platform/tree/develop/vendor/genivi/modules/vssandroidservice

5. Based on conclusions from point 4, TietoEVRY proposed - since kotlin implementation needs to be rewritten eventually - to provide Java implementation containing:

• Proper buildsystem support: Android.bp for future platform integration + gradle for development
• AIDL definition that is more developer friendly and can be easily kept as "compiled" .jar library for 3rd party development of Applications
• Functionality of Service will be the same as BWM kotlin implementation
• MPL 2.0 license

Tuesday 24 March - 500pm CET

...