创建iOS“内部和特设”证书选项已禁用 [英] Create iOS "In-House and Ad Hoc" certificate option disabled
问题描述
我的客户的iOS内部配置资料即将在两周内过期。
所以为了更新它们，我想创建一个新的内部证书。但是当点击添加时，内部和特别选项被禁用。可能是什么原因造成的？
My client's iOS In-House provisioning profiles are about to expire in 2 weeks. So to renew them, I wanted to create a new In-House certificate. But when clicking "Add" the In-House and Ad Hoc option is disabled. What could be the cause of this?
我昨天续签了客户的企业许可证。可能需要一些时间再次创建内部证书吗？ （在我所有其他客户的（非企业）账户上，它有效）
I renewed the client's enterprise license yesterday. Could it be that it takes some time before i can create In-House certificates again? (On all my other client's (non enterpriese) accounts it works)
推荐答案
我是我公司企业账户的代理人您的问题主要如上所述：存在两个企业证书。我有点困惑的地方是为什么你有多个人作为你的代理。 Apple已设置企业帐户&门户网站的方式是，有一个公司范围的代理商可以完全控制该企业分发证书，并且与他/她的CSR /私钥配对。如果你真的想要做到这一点，你需要掌握负责账户的实际代理人并让他出口用于签署CSR&账户的私钥。分发证书，以便您可以反对它。如果您不是为企业部署进行最终生产构建的实体，我建议您更好地与代理协调您的工作，因为他可能有您不知道的计划。
I'm an Agent for my company's Enterprise account and your issue is mainly as laid out above: the existence of two Enterprise certs. Where I'm slightly confused is why you have multiple folks working as your Agent. Apple has setup the Enterprise account & portal in such a way that there is to be one company-wide Agent that has complete control over that Enterprise Distribution certificate and it is paired with his/her CSR/private key. If you really want to do this properly you need to get a hold of the actual Agent in charge of the account and get him to export his private key used to sign the CSR & Distribution Cert so you can develop against it. If you're NOT the entity doing the final production builds for Enterprise deployment I would suggest better coordinating your efforts with the Agent as he may have a plan you're not aware of.
关于Apple在一年多前开始这样做的多个证书，这样您就可以顺利切换到应用程序中的新分发证书，而无需同时更新以前单一证书上的所有应用程序。
Regarding the multiple certificates Apple started doing that over a year ago so that you can smoothly cutover to a new Distribution Cert in your apps without scrambling to update all apps on the previously singular cert simultaneously.
最后需要注意的一点是，虽然证书有效期为3年，但您的配置文件仍将在12个月后到期，以确保您的客户安排更新和更新。适当的维持节奏。
Lastly one point to note is that while the certificate is good for 3 years your provisioning profile will still expire in 12 months time to make sure your client is scheduling their update & maintenance cadence appropriately.
请随时向我提出任何问题。祝你好运！
Feel free to shoot me any questions on this. Good luck!
代理角色是指一个人充当该公司的看门人。这对于大型公司抽出多个内部应用程序确实存在问题，但控制因素有助于维持一个有凝聚力的环境。
The Agent role is meant for one person to act as a gatekeeper for that company. It's does create a problem for a large company pumping out multiple in-house apps but the control factor helps maintain a cohesive environment.
如果您要开始遇到麻烦，那么当您的原始证书设置为过期时，您需要将其转到较新的证书上已创建代理访问。他/她将不得不为您编译代码或从钥匙串访问中导出他们的私钥，以便您可以使用更新的Enterprise Dist Cert。
Where you're going to start getting into trouble is when your original cert is set to expire and you need to roll them over to the newer cert the other person who has Agent access created. He/she is going to have to either compile your code for you or export their private key out of keychain access so that you can use that newer Enterprise Dist Cert.
通常情况下，代理商会创建第一个证书，并且所有内部应用程序都会签名。该证书可能会在2016年到期作为一个例子。 prov配置文件将每年到期，但每个应用程序需要至少每12个月更新一次，以使用新的prov配置文件刷新自己。快到2015年底，你正在盯着即将到期的证书。您将创建替换证书，使用新证书更新每个活动应用程序的配置文件（在2019年到期），然后在2016证书过期之前使用附加到新证书的新prov配置文件更新每个应用程序。
What should typically happen is an Agent creates the first cert and all in-house apps are signed to it. That cert may expire in 2016 as an example. The prov profiles will expire every year, though so each app needs to take an update at least every 12 months to refresh itself with a new prov profile. Fast fwd to the end of 2015 and you're staring down an expiring cert. You'd create the replacement cert, update the provisioning profiles for each active app with the new cert (expires in say 2019), then update each app with the new prov profile attached to the new cert before the 2016 cert goes stale.
有意义吗？
这篇关于创建iOS“内部和特设”证书选项已禁用的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
