[Hackathon Use Case] - FDC3 Share Identity between applications

[Yannick-Malins]

FDC3 Share Identity between applications

Business Problem

Implementing SSO for every application can be a pain, especially if these applications are running in various different containers (standalone, browser, fdc3 container...)

We already have highly secure applications, such as Symphony, running on the user's desktop. Why don't we leverage FDC3 to allow one FDC3 application to share the user's identity with others?

Expected Features

• Mock up an FDC3-enabled webapp+backend that requires users to log in
• Add an option to "pull identity from FDC3", which will trigger a new "GetIdentity" intent
• Extend Symphony to process this intent, trigger a dialog allowing the user to share their identity over FDC3
• Implement a basic token+certificate based verification system between the calling app and Symphony (aka "oauth-ish")

Useful apps, systems, projects, technologies, libraries and datasets

• Symphony
• An FDC3 desktop agent or container

[robmoffat]

Some context: finos/FDC3#684

[Yannick-Malins]

participants:
https://github.com/Yannick-Symphony
https://github.com/ystxn
https://github.com/tzhao-symphony
https://github.com/antoinerollindev
https://github.com/yinan-symphony

[Yannick-Malins]

https://drive.google.com/file/d/1N05MeL6IkKhOsG8SqmdVMRJEVUcJL3LK/view?usp=sharing