Skip to main content
Participant
January 10, 2018
Answered

VDI/SSO Licensing

  • January 10, 2018
  • 2 replies
  • 1778 views

I'm looking for a way to make Adobe products available to our users in their Non-Persistent VDI environments.  Serialization and limiting access would have worked, but in the named user model its a struggle...

Enter Enterprise licensing with SSO.  Perfect!  Except its not seamless SSO (so they have to login every time instead of autologging in with the logged in user's federated identity like other products)... Also it doesn't log the user out or make any changes to the 2 device rule which means every 3rd day they have to answer an extra prompt about signing out other computers.

Is there anyway to make this work as it is now??

Really Seamless SSO & an option to set an auto logoff for authenticated machines from the cloud side or even the installer side would make this work perfectly.  Assign users licenses, they auto activate when they log-in and auto deactivate on a schedule (or via script at logoff?).

Its extremely frustrating to try everything in our power to license this software correctly only to have the worst user experience while actually using it.

Any ideas?

    This topic has been closed for replies.
    Correct answer rpandita

    Hi jhstroebel ,

    Our products are not optimized to work in DoD environments yet. This is because in case of a serialized deployment, licensing is saved in the system profile whereas in case of named user licensing, it gets saved in a user's profile. While the contents of a system folder are retained for a non persistent DoD, the contents of the user profile data do not get saved hence the limitation.

    For SSO, there will be a challenge on the 3rd day when a user logs in because of the 2 machine rule already exhausted even if you setup the user to be authenticated by means of a Kerberos token which can pick up the user's login credentials from the logged in windows user but then 2 machine rule would still hold.

    ~Rohit

    2 replies

    rpandita
    rpanditaCorrect answer
    Inspiring
    January 10, 2018

    Hi jhstroebel ,

    Our products are not optimized to work in DoD environments yet. This is because in case of a serialized deployment, licensing is saved in the system profile whereas in case of named user licensing, it gets saved in a user's profile. While the contents of a system folder are retained for a non persistent DoD, the contents of the user profile data do not get saved hence the limitation.

    For SSO, there will be a challenge on the 3rd day when a user logs in because of the 2 machine rule already exhausted even if you setup the user to be authenticated by means of a Kerberos token which can pick up the user's login credentials from the logged in windows user but then 2 machine rule would still hold.

    ~Rohit

    Participant
    October 4, 2019

    .