If you're using Jamf Cloud, I've found that it requires TLS 1.2. You could also potentially hit that with an on-prem installation of Jamf, depending on your corporate server standards. Typically, the fix is as simple as enabling strong cryptography on your App Portal server (SchUseStrongCrypto registry key under .NET Framework). I have a REG file that I use for this. Many people use a PowerShell script for the same. Here are a couple links to references that explain what's going on and how to fix it...
I should also mention that App Portal's integration with Jamf/Casper was developed for (and tested against) the on-prem version of Jamf only. I've personally configured it with Jamf Pro Cloud (not to be confused with their Jamf Now offering, which is different and not compatible), so I know it mostly works there, too. Just be aware that it hasn't yet officially been tested/supported with Jamf Cloud. That's on the Engineering team's roadmap, but for now, I can tell you that the only thing I've found that App Portal doesn't accommodate is the use of a cloud distribution point. As long as you have at least one on-prem distribution point for Jamf, you should be fine.
Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".
Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".
If you're using Jamf Cloud, I've found that it requires TLS 1.2. You could also potentially hit that with an on-prem installation of Jamf, depending on your corporate server standards. Typically, the fix is as simple as enabling strong cryptography on your App Portal server (SchUseStrongCrypto registry key under .NET Framework). I have a REG file that I use for this. Many people use a PowerShell script for the same. Here are a couple links to references that explain what's going on and how to fix it...
I should also mention that App Portal's integration with Jamf/Casper was developed for (and tested against) the on-prem version of Jamf only. I've personally configured it with Jamf Pro Cloud (not to be confused with their Jamf Now offering, which is different and not compatible), so I know it mostly works there, too. Just be aware that it hasn't yet officially been tested/supported with Jamf Cloud. That's on the Engineering team's roadmap, but for now, I can tell you that the only thing I've found that App Portal doesn't accommodate is the use of a cloud distribution point. As long as you have at least one on-prem distribution point for Jamf, you should be fine.
Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".
To expand on the cloud distribution point item referenced in my earlier post, if you have a need to use a cloud distribution point, you can still do so; however, you will have to initially select an on-prem distribution point when creating the catalog item in App Portal. After the catalog item has been created, you can go into Jamf's admin console and modify the deployment properties to use the cloud distribution point. It just won't appear in the list of available options during the create catalog item wizard.
Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".
No need for manual API integration. Within the product (and our documentation), we still reference JAMF as Casper, so that's what you're looking for within the site settings in the UI. Here's where you'll find documentation on configuring the integration:
Anything expressed here is my own view and not necessarily that of my employer, Flexera. If my reply answers a question you have raised, please click "ACCEPT AS SOLUTION".
