MichaelF45
Bit poster
The following scenario:
A Windows application is used by multiple (20++) users, each in their own instance. These are to run centrally on an external server. The authentication should be done via SAML, where 8 IdPs (coming e.g. from ADFS) have to be connected. There is no other connection between the external server and the local ADs, e.g. no AD Thrust. The application must at least be informed about the underlying SAML user. The individual user sessions are not needed to be persisted (temporary profiles are ok). A simple file exchange between the application on the server and the client environment is necessary.
No decision has been made yet whether to have a native connection application on the client (similar to the normal terminal client aka mstsc) or to do it entirely through the browser.
Question: Is this possible with Parallels RAS? If yes: How much effort - architecturally and financially - can be expected?
A Windows application is used by multiple (20++) users, each in their own instance. These are to run centrally on an external server. The authentication should be done via SAML, where 8 IdPs (coming e.g. from ADFS) have to be connected. There is no other connection between the external server and the local ADs, e.g. no AD Thrust. The application must at least be informed about the underlying SAML user. The individual user sessions are not needed to be persisted (temporary profiles are ok). A simple file exchange between the application on the server and the client environment is necessary.
No decision has been made yet whether to have a native connection application on the client (similar to the normal terminal client aka mstsc) or to do it entirely through the browser.
Question: Is this possible with Parallels RAS? If yes: How much effort - architecturally and financially - can be expected?