Apple Certificates - Revision history

80.229.4.125: /* Get openssl */

2024-07-29T15:40:11Z

Get openssl

← Older revision		Revision as of 15:40, 29 July 2024
Line 14:		Line 14:
	It's because "OpenSSL 3.x changed its default algorithm in pkcs12. Which is not compatible with embedded Security frameworks in macOS/iOS. You could alternatively use OpenSSL 1.x."		It's because "OpenSSL 3.x changed its default algorithm in pkcs12. Which is not compatible with embedded Security frameworks in macOS/iOS. You could alternatively use OpenSSL 1.x."
	</syntaxhighlight>		</syntaxhighlight>

			c:\Program Files\OpenSSL-Win64-1-1-1\bin

	=== Create a certificate signing request (CSR) ===		=== Create a certificate signing request (CSR) ===

85.255.235.105: /* Get openssl */

2024-05-08T15:43:07Z

Get openssl

← Older revision		Revision as of 15:43, 8 May 2024
Line 4:		Line 4:

	download open ssl 1.x (later versions are not compatible with mac ios see comment below)		download open ssl 1.x (later versions are not compatible with mac ios see comment below)

			So something like OpenSSL-Win64-1-1-1

	<syntaxhighlight>		<syntaxhighlight>

80.229.4.125 at 17:36, 13 December 2023

2023-12-13T17:36:08Z

← Older revision		Revision as of 17:36, 13 December 2023
Line 16:		Line 16:

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	openssl genpkey -algorithm RSA -out d:\\~~4Roads_Distribution~~.key		openssl genpkey -algorithm RSA -out d:\\distribution.key

	openssl req -new -key d:\\~~4Roads_Distribution~~.key -out d:\\~~4Roads_Distribution~~.csr -subj "/emailAddress=~~Robert.Nash~~@~~4-roads~~.com, CN=~~4 Roads LTD~~, C=GB"		openssl req -new -key d:\\distribution.key -out d:\\distribution.csr -subj "/emailAddress=you@domain.com, CN=Your Company, C=GB"
	</syntaxhighlight>		</syntaxhighlight>

Line 29:		Line 29:
	* Create New Certificate		* Create New Certificate
	** Choose "Apple Distribution"		** Choose "Apple Distribution"
	** Upload the csr file created above		** Upload the distribution.csr file created above
	** Download the distribution.cer file		** Download the distribution.cer file

Line 40:		Line 40:
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	openssl x509 -in d:\\distribution.cer -inform DER -out d:\\distribution.pem -outform PEM		openssl x509 -in d:\\distribution.cer -inform DER -out d:\\distribution.pem -outform PEM
	openssl pkcs12 -export -inkey d:\\~~4Roads_Distribution~~.key -in d:\\distribution.pem -out d:\\~~4Roads_Distribution~~.p12		openssl pkcs12 -export -inkey d:\\distribution.key -in d:\\distribution.pem -out d:\\distribution.p12
	</syntaxhighlight>		</syntaxhighlight>

Line 83:		Line 83:
	You should now have 2 files in the relevant secure files area of the pipeline		You should now have 2 files in the relevant secure files area of the pipeline

	*~~4Roads_Distribution~~.p12		*distribution.p12
	*yourapp.mobileprovision		*yourapp.mobileprovision

Line 93:		Line 93:
	displayName: 'iOS certificate installation'		displayName: 'iOS certificate installation'
	inputs:		inputs:
	certSecureFile: '~~4Roads_Distribution~~.p12'		certSecureFile: 'distribution.p12'
	certPwd: '$(p12passwd)'		certPwd: '$(p12passwd)'

80.229.4.125: /* Check the build pipeline */

2023-12-13T17:33:56Z

Check the build pipeline

← Older revision		Revision as of 17:33, 13 December 2023
Line 83:		Line 83:
	You should now have 2 files in the relevant secure files area of the pipeline		You should now have 2 files in the relevant secure files area of the pipeline

	*~~{distribution}~~.p12		*4Roads_Distribution.p12
	*{yourapp}.mobileprovision		*yourapp.mobileprovision

	Ensure they are correctly referenced in the build pipeline		Ensure they are correctly referenced in the build pipeline
Line 100:		Line 100:
	inputs:		inputs:
	provisioningProfileLocation: 'secureFiles'		provisioningProfileLocation: 'secureFiles'
	provProfileSecureFile: '{yourapp}.mobileprovision'		provProfileSecureFile: 'yourapp.mobileprovision'

	</syntaxhighlight>		</syntaxhighlight>

80.229.4.125: /* Provisioning File */

2023-12-13T17:33:30Z

Provisioning File

← Older revision		Revision as of 17:33, 13 December 2023
Line 73:		Line 73:
	* Save the changes		* Save the changes

	* Download the mobile provision file so for example {yourapp}.mobileprovision		* Download the mobile provision file so for example yourapp.mobileprovision

	* Upload the file into the secure files area as per the p12 file earlier		* Upload the file into the secure files area as per the p12 file earlier

	=== Check the build pipeline ===		=== Check the build pipeline ===

80.229.4.125: /* Check the build pipeline */

2023-12-13T17:32:29Z

Check the build pipeline

← Older revision		Revision as of 17:32, 13 December 2023
Line 79:		Line 79:
	=== Check the build pipeline ===		=== Check the build pipeline ===

	Check the pipeline build file to ensure that the filenames are correct, note the variable for the p12 ~~file pwd~~		Check the pipeline build file to ensure that the filenames are correct, note the variable for the p12 password $(p12passwd)

	You should now have 2 files in the relevant secure files area of the pipeline		You should now have 2 files in the relevant secure files area of the pipeline

80.229.4.125: /* Upload your distribution p12 file into devops */

2023-12-13T17:31:52Z

Upload your distribution p12 file into devops

← Older revision		Revision as of 17:31, 13 December 2023
Line 51:		Line 51:
	</syntaxhighlight>		</syntaxhighlight>

	You may also need to update the password variable used by devops ~~to import the certificate~~, usually this is called p12passwd and is stored in the build pipeline variables		You may also need to update the password variable used by devops, usually this is called p12passwd and is stored in the build pipeline variables

	(DO NOT HARDCODE IT INTO THE YAML BUILD FILE)		(DO NOT HARDCODE IT INTO THE YAML BUILD FILE)

80.229.4.125: /* Check the build pipeline */

2023-12-13T17:31:11Z

Check the build pipeline

← Older revision		Revision as of 17:31, 13 December 2023
Line 83:		Line 83:
	You should now have 2 files in the relevant secure files area of the pipeline		You should now have 2 files in the relevant secure files area of the pipeline

	{distribution}.p12		*{distribution}.p12
	{yourapp}.mobileprovision		*{yourapp}.mobileprovision

	Ensure they are correctly referenced in the build pipeline		Ensure they are correctly referenced in the build pipeline

80.229.4.125: /* Check the build pipeline */

2023-12-13T17:30:43Z

Check the build pipeline

← Older revision		Revision as of 17:30, 13 December 2023
Line 80:		Line 80:

	Check the pipeline build file to ensure that the filenames are correct, note the variable for the p12 file pwd		Check the pipeline build file to ensure that the filenames are correct, note the variable for the p12 file pwd

			You should now have 2 files in the relevant secure files area of the pipeline

			{distribution}.p12
			{yourapp}.mobileprovision

			Ensure they are correctly referenced in the build pipeline

	<syntaxhighlight>		<syntaxhighlight>
Line 96:		Line 103:

	</syntaxhighlight>		</syntaxhighlight>


	=== References ===		=== References ===

80.229.4.125: /* Upload your distribution p12 file into devops */

2023-12-13T17:28:43Z

Upload your distribution p12 file into devops

← Older revision		Revision as of 17:28, 13 December 2023
Line 53:		Line 53:
	You may also need to update the password variable used by devops to import the certificate, usually this is called p12passwd and is stored in the build pipeline variables		You may also need to update the password variable used by devops to import the certificate, usually this is called p12passwd and is stored in the build pipeline variables

	(DO NOT HARDCODE IT INTO THE ~~yaml build file~~)		(DO NOT HARDCODE IT INTO THE YAML BUILD FILE)

	=== Provisioning File ===		=== Provisioning File ===