Skip to main content
C
ca4of8
Participant
January 14, 2020
Answered

Shared Device License Lab - Student login issues

  • January 14, 2020
  • 2 replies
  • 1675 views

Hello All, 

We have recently migrated to Shared Device Licensing and pushed out various CC programs via JAMF MDM successfully. The problem we're running into is students logging and out. Our current procedure for MacOS is as follows: 

 

Beginning of class instruction:

Student login to lab device, Open Creative Cloud Application, login to CC Application using Federated ID Credentials, Open desired Adobe CC service. 

End of class instruction: 

Save work instance, Sign out of all Adobe CC services (including the CC Application), Log out of lab device.

---

First class session to do this had no issues. The second class session in the lab had issues with logging in. This manifested in CC Application automatically logging students in to previously logged in students who deviated from the previously stated process.

For example, 2nd session student tries to open Illustrator before opening CC Application, login window auto login to 1st session student. Opening CC Application afterwards has 1st session student logged in. At this point in order to switch accounts, student needs to sign out of both CC Application and Illustrator (Help > sign out), then close both. Re-Open CC Application, login, then open Illustrator.

 

Instructor walked to each device during 2nd session and logged out each student according our original procedure, all devices were confirmed to be logged out of Adobe CC services. During 3rd session some students were still affected by this. Any information or assitance would be appreciated.

Correct answer Nikhil R Gupta

Hello,

Shared Device Licenses won't work with the public machine accounts simply due to the fact that while a student can log out of their Adobe account, the SSO session isn't killed. We utilize the Windows credential manager for storing the licensing info which wouldn't fair well in shared OS accounts which is what is causing the issues your students are running into. On MAC the user information will be saved in Keychain. Recomemnded workflow is to have users their own user accounts on the shared machines.

 

Thanks,
Nikhil Gupta

2 replies

J
Jan Doe
Participant
August 6, 2025
Adobe_Sign_Out_Steps.png
S
Community Manager
SuJoshiCommunity Manager
Community Manager
January 23, 2020

Hi,

Kindly confirm if the students of the second session are using the same window/machine account which was used by first session students. If yes, then I would recommend you to use different windows/machines account for different students which might fix your issue. 

 

    C
    ca4of8Author
    Participant
    January 23, 2020

    Can confirm, students in the second session are using the same lab devices
    [MacBook Air (13-inch Early 2015)], and the campus wide generic student
    user account. With further testing, logging out of the user and then back
    in (even as same generic user) seems to clear the issue.

    //edit remove email reply signature

      Nikhil R Gupta
      Community Manager
      Nikhil R GuptaCommunity ManagerCorrect answer
      Community Manager
      January 24, 2020

      Hello,

      Shared Device Licenses won't work with the public machine accounts simply due to the fact that while a student can log out of their Adobe account, the SSO session isn't killed. We utilize the Windows credential manager for storing the licensing info which wouldn't fair well in shared OS accounts which is what is causing the issues your students are running into. On MAC the user information will be saved in Keychain. Recomemnded workflow is to have users their own user accounts on the shared machines.

       

      Thanks,
      Nikhil Gupta

        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices