The following section is primarily a “state of the world” discussion of current Adobe licensing and deployment methods. If you’d rather skip the wall of text and go straight to the technical details, click here.
Among the many common tasks of a Munki admin, dealing with Adobe will be one that consistently generates sighs, groans, and binge drinking. Veteran Munki admins are no stranger to the constant supply of hilarity provided by deploying Adobe packages, and it’s a common topic of discussion. As of writing time, there are 697 results for “Adobe” on Munki-Dev.
The Munki wiki itself has pages devoted to handling Adobe products all the way back to CS3. I wrote a significant chunk of the current wiki page on handling Adobe CC, and that was back when the 2015 versions were the first CC products to deal with.
Now, of course, it’s all changed again as Adobe has introduced new “hyperdrive” style packages from Creative Cloud Packager (CCP), which required yet more work from the Munki developers to accommodate. While the actual installer package might be slightly more sane and operate slightly faster, the overall process for generating and deploying them hasn’t changed much.
As you might infer from all of this, packaging, preparing, and deploying Adobe software has been an ongoing struggle, with no signs of lightening up.
Licensing Is My Favorite Thing, Just Like Sausage Made Of Balsa Wood
For the release of the Adobe CC products, Adobe also introduced a new licensing style – “named” as opposed to the previous “serialized.” CCP allowed you to generate packages that would install the products in either Named or Serialized format, but they required completely different work on the backend.
“Serialized” Adobe products are what most admins are used to, and most admins are likely deploying, due to the Byzantine nature of Adobe licensing for enterprises.
From a technical point of view, though, “Serialized” is a simple concept – you install the product itself, and then you install the license as well. The license on the computer is an opaque black box that Adobe manages that determines what software is or isn’t allowed to run, or maybe will expire in 32,767 days. When you install new products, you reapply the license. Simple in concept.
Oh, except for the part where uninstalling a single serialized product would remove the license for all serialized products.
What’s In A Name?
“Named” licenses are also simple in concept, and actually more simple in execution as well. A “named” license product is only available to a user via an Adobe ID, through the Creative Cloud Desktop App (CCDA). This requires a fundamentally different licensing agreement with Adobe than “serialized” licenses, which is why most Munki admins and Apple techs in general don’t have much control over it – we aren’t usually the ones who sign the Dump Trucks Full Of Money™ agreements with vendors. Someone in Upper Management™ usually makes those decisions, and often without any input from the people who have to do the bulk of the work.
If you’re lucky enough to have an ETLA style agreement with Adobe, or Creative Cloud For Teams, you can probably use “named” licenses. The fun part is that you can have license agreements for both “named” and “serialized”, either together, or separate, that may expire or require renewal at different times.
The good news, though, is that “named” licensing doesn’t really require that much extra work. There’s no license package that needs to be installed on the client, and Adobe’s CCDA basically does all the work for determining what software users are allowed to use. From a technical standpoint, this is much easier for both users and IT operators, because there’s just less surface area for things to go wrong.
With “named” licensing and the CCDA, there aren’t real “releases” anymore. Rather than releasing yearly (or more) product cycles like the old “Creative Suite” 1-6, product changes are released in smaller increments more regularly, and the CCDA keeps things up to date without the admins having to necessarily rebuild packages every time.
Although there’s no official word on this, my suspicion (and this is entirely my personal opinion) is that “serialized” licensing will eventually disappear. We’re already seeing products released only on CCDA via named licensing (Adobe Experience Manager), which to me sounds like a death knell for the old “build serial packages and send them off” system.
So if you read the writing on the wall that way, the future for building serialized packages via CCP seems grim (as if the present use of CCP wasn’t already dystopian enough). I’m frustrated enough with CCP, Adobe packages, and “Adobe setup error 79” that I’m actually looking forward to a named-license only environment.
But of course, we don’t want to lose the functionality we get with Munki. Allowing users to decide what software they get and allowing them to pick things on-demand is one of the most useful features of Munki itself!
Now that I’ve spent 800 words covering the context, let’s talk about implementation.
Craft Your Casus Belli, Claim Your Rightful Domain
The ultimate goal of this process is to set up named licensing, get our users loaded or synced up into it, and provide access to the software entitlements we’ve paid for.
There’s lots of ways to go about this, but as is Facebook custom, we like solving problems by over-engineering the living daylights out of them. So my methodology is to try and set up all the pieces I need for self service by utilizing Adobe’s User Management API. We want this process to be as user-driven as possible, mostly so that I don’t have to do all the work.
The Org-Specific Technical Stuff
If you aren’t already familiar with it, the Adobe Enterprise Dashboard is the central location for managing Adobe named licenses. In order to maximize our integration, we want to use Federated IDs, where accounts are linked to our Active Directory (AD) infra. There’s various pros and cons to this, but if you’ve already got an AD + SAML setup, this is a good use case for it.
Step one in this phase of the process is Claiming Your Domain, where we claim ownership over the domain matching the email addresses we expect our users to authenticate with. This does require submitting a claim to Adobe, and they verify it and provide a TXT record that must be served by your outward-facing DNS (so Adobe can verify that you own the domain you say you do).
Once your domain is claimed and set up, we wanted to utilize our Single Sign On (SSO) capability. Adobe uses Okta to connect to an SAML 2.0-compatible SSO environment, so you and the team that manages your identity settings will need to do some work with Adobe to make that work.
The details of this process are documented in the links above, and is generally specific to your organization, so there’s no need to go into details here.
Learning To Fly (with the API)
Despite me covering it in three paragraphs, the above section took me the most amount of work – mostly because so much that was out of my control. Once you get past the difficult setup phase, the implementation of the User Management API becomes relatively painless – if you’re familiar with Python.
The good news is that the API is very thoroughly documented.
In order to utilize the API, you need a few pieces:
- A certificate registered in the API
- The private key for the cert for the API to auth with
- The domain variables provided by the API certificate tool
- Three custom Python modules –
- Python (2 or 3) – system Python is fine
First, you’ll need to set up a new Integration in the Adobe I/O portal.
If you don’t have a certificate and its private key already available, you can generate a self-signed one:
$ openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout private.key -out certificate_pub.crt
You can then upload this cert into the Adobe I/O portal.
Adobe doesn’t actually verify the cert for anything except confirmation that the private key and public key match, so there’s no technical reason in terms of the API why you can’t keep using it. It’s always a good practice to use a real certificate, but for initial testing, this works just fine.
Upload the cert to your Integration, and it’ll provide you with the values you’ll need for crafting your config file below.
Once you’ve got a cert and the private key, you can start writing the API script.
SNAAAAAAKE, OH IT’S A SNAAAKE
Adobe’s sample scripts are quite thorough, and they use Python, which works perfectly for Mac admins. The downside, though, is that you’ll need to install three custom modules on any client who is going to use this script to access your API.
There’s a couple of ways to handle this, so it’s up to you to decide which one you want to pursue.
You can do it via
sudo /usr/bin/python -m ensurepip
sudo /usr/bin/python -m pip install --ignore-installed --upgrade requests
sudo /usr/bin/python -m pip install --ignore-installed --upgrade pyjwt
sudo /usr/bin/python -m pip install --ignore-installed --upgrade cryptography
You can download the source for each of those modules and build it manually, and then copy the built modules into a central location on the client where you can load them:
python setup.py build
Whatever method you prefer to use, you need to be able to run the Python interpreter and import each of those modules (specifically
requests) successfully to use the API sample scripts.
The Config File
Next up is the crafting of your config file:
host = usermanagement.adobe.io
endpoint = /v2/usermanagement
ims_host = ims-na1.adobelogin.com
ims_endpoint_jwt = /ims/exchange/jwt
domain = my domain
org_id = my organization id
api_key = my api key/client id
client_secret = my api client secret
tech_acct = my api client technical account
priv_key_filename = my private key filename from above
The values for the
[enterprise] section are all provided by the Integration when you upload the cert you created.
For example, for Facebook, it might look something like this:
domain = facebook
org_id = ABC123@AdobeOrg
api_key = abc123
client_secret = abc-123-456
tech_acct = firstname.lastname@example.org
priv_key_filename = private.key
priv_key_filename must simply be the name (not the path!) of the file that contains your private key that you generated earlier.
Start Your Script
Most of the start of this script is ripped straight from the samples page:
The good news is that this (theoretically) works in both Python 2 or 3 (NOTE: I have not tested this in Python 3).
The initial part of the script just gets us the setup we need to make calls later. We’ll use
jwt to create the JSON Web Token (which itself uses
cryptography to use the “RS256” hashing algorithm to sign the token with the private key), and
requests to make it easy to send GET and POST requests to the API endpoint.
You could write your own GET/POST tools, or use
urllib2 or any pure Python method of accomplishing the same thing;
requests isn’t technically a requirement. It just dramatically simplifies the process, and Adobe’s sample code uses it, so I decided to stick with their solution for now.
The Config Data
Before we can use the API, we’ll need to set up all the required variables and create the access token, the JSON web token, and the config data read from the file we created earlier. The Adobe sample documentation does this directly in a script, but I wanted to make it a bit more modular (i.e. I use functions). It’s a little bit cleaner this way.
First, let’s parse the private key and user config:
Next, we’ll need to craft the JSON web token, which needs to be fed the config data we read from the file earlier, and signed with the private key:
Yes, thank you, I realize “jwt_token” is redundant now that I look at it, but I’m not changing my code, dangit.
With the JWT available, we can craft the access token. This is where
requests really comes in handy:
With all of these functions ready, it’s really easy to combine them together in a single convenient
generate_config() function, which can be used by other public functions to handle all the messy work. The purpose of this function is to load up the config data and private key from a specific location on disk (rather than having to continually paste all of this into the Python interpreter).
Here, we’ve simply stored the private key and config file in
/opt/facebook for easy retrieval. Feel free to replace this path with anything you like. The idea is that these two files – the private key and the config file – will be present on all the client systems that will be making these API calls.
Our config functions are all set up and good to go, so now it’s time to write the functions to actually interact with the Adobe API itself.
Let’s Ask the API For Some Data
All of the Adobe API queries use common headers in their requests. To save ourselves some time, and avoiding having to retype the same thing repeatedly, let’s use a convenient function to return the headers we need:
Now we have all the config pieces we need, let’s ask for some important pieces of data from the API – the product configuration list, the user list, and data about a specific user.
In order to control how much data is sent back from these queries (which can result in rather large sets of data), Adobe automatically paginates each request. These two functions both start at page 0 and continue to loop until the resulting request contains
lastPage = True. Just keep in mind each individual request will only give you a subset of the data.
With a list of product configurations, a list of all users, and the ability to ask for data on any specific user, we actually have nearly all of the data we’ll ever need. Rather than combining these pieces ourselves, we can also query some more specifics.
Here’s how to get a list of all users who currently have a specific product configuration entitlement:
With that data, it’s also easy to get a list of all products a given user has:
Enough Asking, It’s Time For Some Action!
With the above code, we’ve got the ability to ask for just about all the available data that we might care about. Now it’s time to start making some requests to the API that will allow us to make changes.
Hello, Goodbye, Mr. User
The obvious first choice here is the ability to create and remove a user. When I say “create a user”, I really mean “add a federated ID to our domain.” This is different than creating an Adobe ID (and see the links far above to see Adobe’s explanation of the difference between account types). Adobe does provide documentation for creating both types of accounts.
You Get An Entitlement, YOU Get An Entitlement!
The next obvious choice is adding and removing product configurations to and from users:
If you’ve been looking carefully, you’ll note that all of these functions start with
_, indicating that they’re intended to be private module functions. Although Python doesn’t really enforce this, the reason is because I wrote this module to have internal data functions, and external/public convenience functions.
The public functions are all meant to be completely independent. The necessary work of generating the config data (the access token, JWT, etc.) should be abstracted away from the public use of these tools, and therefore we need internal functions to do all this work for us, and external public functions that others can call without needing to understand what they do.
We’ve covered all the private module functions, so now let’s get into the convenient public functions.
I’m Doing It For The Publicity
The public functions here should represent common queries that someone might want to use this module for.
Let’s start by providing a convenient list of Adobe product configurations:
Take a look at this function, because you’ll see this same general strategy in all the rest of the public functions. We generate the config on the first line – by reading from the files on disk, and crafting the pieces we need on-demand. The config tuple is then used to feed the internal functions (in this case,
_product_list() ). The end result is we get a nice Python list of all the product configurations, without any other unnecessary data.
We can do the same thing with users:
Note that these two functions are essentially identical.
Straightforward request: does a user exist in our domain? Does this user already have a federated ID?
Note that the above function can be slightly misleading. It only returns
True if the user’s type is “federated ID”. This doesn’t technically answer the question of “does this user exist at all”, but specifically answers “does this federated ID exist”?
Another useful query: does the user have a specific product entitlement?
While we’re on the topic of user management, here are public functions for adding and removing users:
Finally, we get the last pieces we want – public functions to add and remove product entitlements to users:
This module, all together, creates the
adobe_tools Python module.
So… What Do I Do With This?
We have a good start here, but this is just the code to interact with the API. The ultimate goal is a user-driven self-service interaction with the API so that users can add themselves and get whatever products they want.
In order for Munki to make use of this, this module, along with the usermanagement.config and private.key files above, needs to be installed on your clients. There are a few different ways to make that happen, but shipping custom Python modules is outside the scope of this post. Suffice to say, let’s assume that you get to the point where opening up the Python interpreter and typing
import adobe_tools works.
We’re going to use Munki to make that happen, but we’ll need a little bit more code first.
Adding A User And Their Product On-Demand
Before we get into the Munki portion, let’s solve the first problem: easily adding a product to a user. We have all the building blocks in the module above, but now we need to put it together into a cohesive script.
This is the “add_adobe.py” script:
You run this script and pass it a product configuration. It detects the current logged in user, and if that user doesn’t already have a federated ID, it creates one. Then it checks to see if the user already has that product entitlement, and if not, it adds that product to the user.
There’s a bit of handwaving done there, and some assumptions made – especially in regards to the logged in user and the email account. If you already have an existing mechanism for obtaining this data (such as code for doing LDAP queries, or some other endpoint/database you can query for this info), you can easily add that in.
This script needs to go somewhere accessible on your clients, so put it anywhere you think makes sense –
/opt/yourcompany/bin or anything like that. That’s up to you.
Feeding the Munki
At this point, we’ve got four items on the clients that we need:
We’ve made the simple assumption that
/opt/facebook/lib is in the Python PATH (as shown in the gist above, we can use a simple
sys.path.append() to ensure that).
The only part left is providing the actual Munki items for users to interact with via Managed Software Center.app.
Although it isn’t covered in depth on the wiki, we can use Munki “nopkg” type items to simply run scripts without installing any packages. We’re going to combine this with using OnDemand style items so that users can click the “Install” button to get results done, but there’s no persistent state being checked. This essentially means we run the script every time the user clicks the button, which is why it’s important to be idempotent.
With everything on the client, our pkginfo is quite simple:
Note that Adobe Creative Cloud Desktop App is listed as a requirement. That’s not entirely true, but I think it makes a bit more sense for the user that they get all the pieces they need to actually use the software after clicking the Install button.
I’ve also added in the icon for Photoshop CC, although that’s purely cosmetic.
Add this pkginfo to your repo, run
makecatalogs, and try it out! Logs look something like this:
After that, log into Adobe CCDA and the software will be listed there for installation.
Now Add Them All!
Add one of these pkginfos for each of your product configurations that you want users to select. The end result looks kind of nice:
After clicking all of the buttons, CCDA looks very satisfied:
Self-service Adobe CCDA app selection, using Munki and the Adobe User Management API. No more packaging, no more CCP!
Some Caveats and Criticisms
Despite the niftiness of this approach, there’s some issues to be aware of.
The API Key Is A Megaphone
The main problem with this approach is that the API private key has no granular access over what it can and can’t do. The only thing you can’t do with the API private key is make a given user a “System Administrator” on the Enterprise dashboard. But you can add and remove user accounts, add and remove product entitlements to users, and make users product admins of whatever they want.
In most cases, this isn’t a huge deal, but there’s some potential for mischief here. If every single client machine has the private key and necessary config data to make requests to the API, any single client can do something like “remove all users from the domain.” What happens to your data stored in Creative Cloud if your federated ID is removed? I imagine we’d probably prefer not to find out the nuances of having your account removed while using it.
There are some different ideas to address this, though. Instead of storing the key and usermanagement config file on the disk persistently, we could potentially query an endpoint hosted internally for them and use them for the duration of the script. In this theoretical scenario, you could control access to that endpoint, perhaps requiring users to authenticate ahead of time, or logging / controlling access to it.
One thing I didn’t mention above at all is that the number of requests in a given time frame need to be throttled. Adobe has great documentation on this, including some exponential back-off code samples. We didn’t implement any of this in this initial proof-of-concept, but if you’re going to roll this to a large production environment, you’ll almost certainly need to handle the return value indicating “too many requests.”
If you wanted to take this further, we could actually turn off OnDemand for these Munki items. Using an
installcheck_script, we could query whether or not a given product was added for a given user, and that would change the state of the “Add Photoshop CC To My Panel” to installed, and thus the button in Munki would correspond to “Add or Remove this app from my account.”
Generally, what I suspect is that most users will probably never particularly want to remove a product entitlement from themselves, since it doesn’t actually correspond to what’s installed or not. So changing Munki to reflect state probably doesn’t accomplish too much.
No Way To Trigger Installs
The only major feature request I really wish existed was a way to trigger CCDA into installing a product entitlement. All we can do is add or remove the entitlements to user accounts, but we can’t actually install them for the user (through CCDA).
You could build a Named license package through CCP and actually distribute that directly in your Munki repo, but then you’re essentially back to the same point you were before: you still need to add the entitlement to the user, you still need to package each release / new version of the product, and you still need close to 60 GB (or more!) to store all of the CC packages. About the only thing you’re doing differently compared to serialized licenses is that you don’t have to worry about the serialization package anymore.
You can trigger updates using Remote Update Manager, but that doesn’t provide a mechanism to “Install Photoshop from CCDA.” So no matter what we do, we still rely on the user to log in to CCDA and press the button.
Bandwidth vs. Network
Because this method relies on the user installing from CCDA, that means the Adobe software is being deployed from the Internet. That means internet bandwidth is used to install these, not local network bandwidth. For orgs with smaller internet pipes, this could be significant cost or time sinks.
As I mentioned above, if bandwidth is an issue, you could package up the named licenses with CCP and distribute them via Munki. That would allow you to use your local network bandwidth rather than internet pipes.
Well, it works.