Importing p12 files with password in Match #19814
Replies: 3 comments 2 replies
-
Hello, I stumbled upon this discussion as I was trying to use match import. After struggling with the import for quite some time, I found out that the key file must be an unencrypted file. At least on MacOS, an encrypted PKCS file cannot be imported with an empty password. As match encrypts the key file anyway, using an encrypted file with an additional password is not important to me. However, it took me quite some time to find out how it works (reading the code and analyzing an existing match repository). It would be nice if the documentation (website and command options) of match import would be improved:
It would be even nicer if the import command would verify the supplied files before adding them to the repository. Another limitation is, that it will only work if the certificate and key file have the same name (if I didn't miss something in the code). |
Beta Was this translation helpful? Give feedback.
-
Is there any progress regarding this feature request? |
Beta Was this translation helpful? Give feedback.
-
As I struggled for a long time today to do this (knowing I successfully did this before): To move an existing Enterprise Certificate/Key Pair from the Keychain Access App to match do the following:
When asked for the .cer file, write Certificates.cer
and upload the result to the "profiles/enterprise" folder of your match repo. |
Beta Was this translation helpful? Give feedback.
-
Hi!
Is it correctly understood that match doens't support importing p12 files with a password yet?
To me it seems like the
Utils.import
in therunner.rb
doesn't pass onCERTIFICATE_PASSWORD
environment variable to theFastlaneCore::KeychainImport.import_file
method.So I was thinking if the
match import
should, or could, take acertificate_password
argument, that would be passed down?Beta Was this translation helpful? Give feedback.
All reactions