Hi @jantonio !

which Authentication Provider are you using? Azure AD? ADFS?

You could configure Azure AD / ADFS as outlined in the OIDC Implementation Guide and setup the external users as “guest accounts”.

Of course you could use Citrix Desktops and implement SSO for your external Users. However, you would still need to use FSM basic authentication for them.

Best regards
Roman

Hi @roklde 

Thank you.

The problem is that the external user is logged into the device with his organization's credentials, even if he is connected to a VPN, the local credentials detected by the FMS client are invalid because they end up not existing.

Well, in this case you will have to make sure that those external accounts are available in your authentication provider. Not sure, if you can implement B2B federation in your authentication provider?

I also assume the browser cookies are playing a role here. When they login with their organization ID prior opening the Smart Client, the session cookie is active and forwarded for authentication. Did you try to use incognito to force login screen of your authentication provider?

Alternatively, you can try it with a Jump Host Server or Citrix Desktop and enforce the external user to login with an SSO ID that is available in your authentication provider.

Or to simplify it use FSM basic authentication for external accounts.

Best regards
Roman