...
The Launcher will to be able to launch applications defined from multiple source, so it will need to connect to multiple FDC3 App Directories. Example applications Application Directories include :
- In house, container hosted, applications. The Enterprise will typically have a single container such as OpenFin, Glue42 or an in-house container.
- 3rd party container hosted applications.
NB In our experience this is not currently a real use case but the goal of FDC3 is to enable this use case - In house applications written in .Net which are installed onto the user' desktops using inhouse installers.
- TR applications from Eikon, which is running on the user's desktop.
...
The launcher prompts the user to logon using the Enterprise's SSO setupsystem.
The launcher has a list of Application Directories Directory URLs it is configured to connect to, and passes the user name and SSO identity/cookie of the logged in user to each App Directory as part of its sign on.
The In-House app directory holding details of the in-house applications uses this identity and internal entitlement information to define what applications this user is permissioned to run. This is reflected in the list of applications the App Directory presents to the user.
...
The Launcher dev team have created the ability to save and restore layouts, possibly by extending capabilities from one or more of the Platforms deployed. They have extended their in-house App Directory to store allow storing and retrieve the saved Layouts available to the logged on user. This capability is also used to make 'standard layouts' available to users. The layouts made available depend on the user's role.