Compliance_and_Identity.pdf

Slide 1

Slide 1 text

No content

Slide 2

Slide 2 text

Slide 3

Slide 3 text

Slide 4

Slide 4 text

Slide 5

Slide 5 text

Slide 6

Slide 6 text

Slide 7

Slide 7 text

Slide 8

Slide 8 text

Slide 9

Slide 9 text

Slide 10

Slide 10 text

Slide 11

Slide 11 text

Slide 12

Slide 12 text

Slide 13

Slide 13 text

Slide 14

Slide 14 text

Slide 15

Slide 15 text

Slide 16

Slide 16 text

Slide 17

Slide 17 text

Slide 18

Slide 18 text

Slide 19

Slide 19 text

Slide 20

Slide 20 text

Slide 21

Slide 21 text

Slide 22

Slide 22 text

Slide 23

Slide 23 text

Slide 24

Slide 24 text

Slide 25

Slide 25 text

Slide 26

Slide 26 text

Slide 27

Slide 27 text

Slide 28

Slide 28 text

Slide 29

Slide 29 text

Slide 30

Slide 30 text

Slide 31

Slide 31 text

Slide 32

Slide 32 text

Slide 33

Slide 33 text

© JAMF Software, LLC ADCS Connector - Prerequisites Windows Server 2016 or higher Be member of the same domain as the PKI or have a trust relationship with that domain .NET 4.5 or higher FQDN Ports (443 for Connector, 135, 49152-65535 for DCOM)

Slide 34

Slide 34 text

Slide 35

Slide 35 text

Slide 36

Slide 36 text

Slide 37

Slide 37 text

Slide 38

Slide 38 text

Slide 39

Slide 39 text

Slide 40

Slide 40 text

Slide 41

Slide 41 text

Slide 42

Slide 42 text

Slide 43

Slide 43 text

Slide 44

Slide 44 text

Slide 45

Slide 45 text

Slide 46

Slide 46 text

Slide 47

Slide 47 text

Slide 48

Slide 48 text

Slide 49

Slide 49 text

Slide 50

Slide 50 text

Slide 51

Slide 51 text

Slide 52

Slide 52 text

Slide 53

Slide 53 text

Slide 54

Slide 54 text

Slide 55

Slide 55 text

Slide 56

Slide 56 text

© JAMF Software, LLC ADCS Connector - Troubleshooting Everything is fine! Logs here C:\inetpub\logs\LogFiles\W3SVC2 2019-09-23 22:07:41 193.108.164.2 GET /api/v1/version - 443 AdcsProxyAccessUser 193.108.165.29 Java-SDK - 200 0 0 12968 2019-09-23 22:07:46 193.108.164.2 POST /api/v1/certificate/request - 443 AdcsProxyAccessUser 193.108.165.29 Java-SDK - 200 0 0 4906 2019-09-23 22:07:46 193.108.164.2 POST /api/v1/certificate/retrieve - 443 AdcsProxyAccessUser 193.108.165.29 Java-SDK - 200 0 0 281 3 steps to acquire the certs, all with answer 200, we get a certificate

Slide 57

Slide 57 text

© JAMF Software, LLC ADCS Connector - Troubleshooting 403 16 error Logs here C:\inetpub\logs\LogFiles\W3SVC2 2019-07-19 09:06:20 10.196.172.64 GET /api/v1/version - 443 - 10.196.172.17 Java-SDK - 403 16 2148204809 0 Usually due to improper Root CA certiﬁcate in Intermediate folder in Windows

Slide 58

Slide 58 text

© JAMF Software, LLC ADCS Connector - Troubleshooting 403 16 error identify and ﬁx Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Move-Item -Destination Cert:\LocalMachine\CA

Slide 59

Slide 59 text

Slide 60

Slide 60 text

© JAMF Software, LLC ADCS Connector - Troubleshooting Other common issues ADCS Connector requires a proper FQDN Jamf Pro says IP or FQDN, only use FQDN Do not break TLS/SSL authentication or replay it GPOs could block authentication

Slide 61

Slide 61 text