Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
Adding missing keys to readme
  • Loading branch information
krypted authored Apr 8, 2019
1 parent 8dc92c9 commit b7ad050
Showing 1 changed file with 11 additions and 14 deletions.
25 changes: 11 additions & 14 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ Get Certificates From Jamf Pro Into Your iOS Apps

## Jamf Certificate SDK

###### Framework Architectures
#### Framework Architectures

The included framework ships with two simulator architectures (i386 and x86_64) and two device architectures
(armv7 and arm64). This allows third-party app developers to use the framework both in their own simulators
Expand All @@ -19,39 +19,37 @@ this.

#### Managed App Config Required Settings

To ensure proper use of the SDK, the iOS app is required to be distributed by Jamf Pro. During distribution, an App Configuration
can be specified that will let the SDK communicate with Jamf Pro and request the proper certificate. Here is a sample App Configuration
that can be used as a basis for your own app.
To ensure proper use of the SDK, the iOS app is required to be distributed by Jamf Pro. During distribution, an App Configuration can be specified that will let the SDK communicate with Jamf Pro and request the proper certificate. Here is a sample App Configuration that can be used as a basis for your own app.

Note that you can add your own key/value pairs to the App Configuration to configure other parts of your app. Jamf's keys are all prefixed
with `com.jamf.config.` so they will not clash with your own naming conventions for keys.
####### Note: You can add your own key/value pairs to the App Configuration to configure other parts of your app. Jamf's keys are all prefixed with `com.jamf.config.` so they will not clash with your own naming conventions for keys.

<dict>
<key>com.jamf.config.jamfpro.invitation</key>
<string>$MOBILEDEVICEAPPINVITE</string>
<key>com.jamf.config.device.udid</key>
<string>$UDID</string>
<key>com.jamf.config.jamfpro.url</key>
<string>https://the_jamf_pro_server_url_goes_here/</string>
<string>https://qpzpaot.kube.jamf.build/</string>
<key>com.jamf.config.certificate-request.pkiId</key>
<string>1</string>
<key>com.jamf.config.certificate-request.template</key>
<string>User2</string>
<string>blah</string>
<key>com.jamf.config.certificate-request.subject</key>
<string>cn=something</string>
<key>com.jamf.config.certificate-request.sanType</key>
<string>rfc822Name</string>
<key>com.jamf.config.certificate-request.sanValue</key>
<string>somebody@example.com</string>
<string>$EMAIL</string>
<key>com.jamf.config.certificate-request.signature</key>
<string>$JAMF_SIGNATURE_com.jamf.config.certificate-request</string>
</dict>

###### MAC key discussion
#### MAC key discussion

com.jamf.config.jamfpro.url: The value should be filled in with your Jamf Pro Server's URL.

The keys prefixed with `com.jamf.config.certificate-request` are used during certificate generation. They will
be specific to your organization. You should confer with those responsible for Jamf Pro and your Certificate Authority to ensure
the proper settings are configured for your app.
be specific to your organization. You should confer with those responsible for Jamf Pro and your Certificate Authority to ensure the proper settings are configured for your app.

* pkiId: (an integer but typed as string in the MAC) Jamf Pro ID of the PKI Integration/Certificate Authority to be used; find this in the Jamf Pro
web UI at Settings > PKI Certificates > Your ADCS CA settings and then look in the URL bar for the number after "id=". You should have a URL something like "adcsSettings.html?id=3"
Expand All @@ -60,5 +58,4 @@ web UI at Settings > PKI Certificates > Your ADCS CA settings and then look in t
* sanType: (string) One of 'rfc822Name', 'dNSName', or 'uniformResourceIdentifier'
* sanValue: (string) Subject Alternative Name to include in the certificate signing request

With the subject and sanValue fields, variable substitution is available as discussed under "Payload Variables for Mobile Device Configuration Profiles" at
http://docs.jamf.com/jamf-pro/administrator-guide/Mobile_Device_Configuration_Profiles.html
With the subject and sanValue fields, variable substitution is available as discussed under "Payload Variables for Mobile Device Configuration Profiles" at http://docs.jamf.com/jamf-pro/administrator-guide/Mobile_Device_Configuration_Profiles.html

0 comments on commit b7ad050

Please sign in to comment.