--- title: "Generating Enterprise Certificate" slug: "generating-enterprise-certificate" updated: 2022-09-26T10:00:33Z published: 2022-09-26T10:00:33Z canonical: "help.pillir.io/generating-enterprise-certificate" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.pillir.io/llms.txt > Use this file to discover all available pages before exploring further. # Generating Enterprise Certificate In the developer site ***developer.apple.com***, the user is registered as a particular organization under an **Enterprise** program or a **Developer** program. The **Enterprise Program** enables the user to generate **Enterprise Certificates** while the **Developer Program** enables the user to generate **App Store Certificates**. For both the certificates there are three major steps. This document holds the information on: 1. How to manually generate **iOS certificates** 2. How to create a **Provisioning Profile** 3. How to create an **App Identifier** (For both App Store and Enterprise Apps) This document aids the customer in generating **Enterprise Certificate** for their Projects. NOTE Both Enterprise and App Store certificates follow the same sequence except for a few minor differences in option selections. Refer to [App Store Certificate](https://help.pillir.io/docs/generating-app-store-certificate) document for understanding how to generate **App Store Certificates**. Based on the role of the user, there are 2 sections available, namely: - **People** - where the user can add people and manage other accounts - **Certificates, Identifiers, and Profiles** - where the user can generate certificates ![image(37)-1](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image(37)-1.png) NOTE The [App Store certificate Homepage](https://help.pillir.io/docs/generating-app-store-certificate) consists of 3 options while the Enterprise homepage does not have the **App Store Connect** option. ## Creating an Enterprise Certificate In the **Certificates, Identifiers and Profiles** section, users can create and generate new certificates and view existing certificates. ![image(39)-2-](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image(39)-2-.png) The users can click the **+ button** to generate a new certificate. Adding a new certificate redirects the user to a page where they are provided with multiple options for creating certificates related to **S****oftware, Services, or Intermediate certificates.** The user can create a Enterprise certificate through the following steps: 1. During certificate generation, the user has to select the option **In-House and Ad Hoc** under the Software section. ![image.png](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image%2838%29.png) NOTE For [App Store certificates](https://help.pillir.io/docs/generating-app-store-certificate#generating-app-store-certificate-), users select the **iOS Distribution** (App Store and Ad Hoc) option. 2. After the In-House and Ad Hoc option is selected, the user clicks **C****ontinue**. 3. The user is requested for a **Certificate Signing Request(CSR)** that needs to be uploaded to generate the new certificate. This is done using the **Keychain Access**. ![image(40)-3](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image(40)-3.png) 4. On opening the Keychain access, the user has to select the **Certificate Assistant** from where they can request a certificate from a Certificate Authority. ![image.png](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image%2841%29.png) 5. This certificate is provided by a certificate authority to the users of a particular organization. It can be accessed by providing the name, email, and details in the **Certificate Assistant** popup of the Keychain Access. ![image(42)-4(1)](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image(42)-4(1).png) The certificate is saved in the local drive. ![image(43)-5](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image(43)-5.png) 6. Once the certificate details are saved, it is uploaded to the developer site.![image(44)-6](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image(44)-6.png) 7. The certificate details such as **Name, Type, Expiration date,** and **Created By** are displayed and the certificate is available for **Download**.![image(45)-7-](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image(45)-7-.png) ## How to generate App Identifiers? The Identifiers page can be accessed from the certificates homepage on the left. While certificates are universally accepted for the company, the App identifiers are uniquely specified for each App created in the platform. ![IdentifiersAdd-blurred](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/IdentifiersAdd-blurred.png) Clicking the **+ button** redirects users to a page with a list of identifiers. Here the users can register a **new App ID** and click **C****ontinue.**![APPid](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/APPid.png) For **Select a typ****e** question, choose **App** and click **Continue.** ![registernewidentifier-blurred](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/registernewidentifier-blurred.png) The ID registration page consists of the following details: 1. **Platform** - where the App is deployed (all the iOS devices) 2. **Description** - A short description of the App needs to be entered 3. **App ID Profile** - Consists of the bundle ID given to a particular app. The general format is ***com.companyname.appname*** 4. **Capabilities** - Multiple App capabilities are listed out. Since Pillir’s EdgeReady Apps only support push notifications, only that capability is enabled. ![registerappid-new-blurred](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/registerappid-new-blurred.png) From the **Capabilities** section, The **Push Notification** option is selected. After the details are given, the user clicks **C****ontinue**. ![push notificaation-new](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/push%20notificaation-new.png) Finally, the user can verify all the entries made and click **Register**. ![ClickRegister](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/ClickRegister.png) The newly created identifier is displayed on the **Identifiers** list. ![Registeredidentifierspage-blurred](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/Registeredidentifierspage-blurred.png) NOTE The bundle ID has to be unique. If a bundle ID with the same name exists already, it throws an error and the identifier cannot be created. ## Steps to create a Production SSL certificate: To configure a push notification for an App ID, a client SSL certificate that allows your notification server to connect to the Apple Push Notification Service is required. The SSL certificate can be generated by the following steps: 1. The push notification can be configured by clicking the newly created **I****dentifier**. ![SSLcerti-clickidentifier-step1-blurred](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SSLcerti-clickidentifier-step1-blurred.png) 2. The user clicks the **Configure** button in the push notification option under the **C****apabilities section**. (*The identifier has to be edited and then configured* ). ![SSLcerti-configure-step2](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SSLcerti-configure-step2.png) 3. A popup opens requesting the Push notification service SSL Certificate for both **Development and Production** environments. ![SSLcerti-popup-step3-blurred](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SSLcerti-popup-step3-blurred.png) NoteDevelopment SSL certificate is meant for developers and works only with Xcode. 4. For deploying the application, we select the **Production environment certificate**. The **Create a New Certificate** page opens. Select the Platform as **iOS** and upload a **Certificate Signing Request(CSR)** file. ![SSLcerti-newcertif-step4](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SSLcerti-newcertif-step4.png) A certificate is generated using the **Certificate Assistant** by entering the respective credentials. ![SSLCertif-certassistant-step5-blurred](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SSLCertif-certassistant-step5-blurred.png) 5. The certificate is **exported** and stored in the local file. ![SSLCert-savetodisk-step6-blurred](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SSLCert-savetodisk-step6-blurred.png) ![SSLCert-savetodisk-step6b-blurred](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SSLCert-savetodisk-step6b-blurred.png) 6. Production environment certificate requests the users to select the **Platform** and a **link(Choose File)** to upload the certificate. ![SSLcert-uploadcert-step7-blurred](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SSLcert-uploadcert-step7-blurred.png) 7. After uploading the certificate, the user clicks **Continue**. Once the certificate is uploaded, it is available for **Download**. The certificate can be **Revoked** if not required. ![SSLCert-download-step8-blurred](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/SSLCert-download-step8-blurred.png) NOTE Similar to the Apple ID certificate, for the production certificate with the App identifier and Push notifications, a CSR certificate needs to be generated. In the Keychain access, using the certificate assistant, a new CSR production certificate is generated. The generated certificate is exported in p12 for multiple user access. ## Steps to create a Provisioning Profile: 1. The user has to create **a Profile for the App store** under the **Distribution** section. Once selected, the user clicks **C****ontinue.** **![](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/image-1628087150418.png)** 2. On clicking the **Continue** button, the screen is redirected to the **P****rofiles page** where the appropriate **Identifier** (created in the previous step) is selected from a dropdown list. Then the user clicks **C****ontinue** to proceed with the next step. ![Provcert-selectappid](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/Provcert-selectappid.png) The user has to select the latest certificate generated from a list of recent certificates. 4. The provisioning profile is given a **Profile Name**. ![Provcert-profilename](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/Provcert-profilename.png) 5. After all the details are furnished, Click **Generate** to go to the next page. 6. Click **Download** to get the **Provisioning Profile**. ![Provcert-download](https://cdn.document360.io/718af901-247b-46be-8ace-83da21839237/Images/Documentation/Provcert-download.png) 6. A newly created profile is displayed in the **Profiles section**. Note 1. Multiple profiles can be created for a single App Identifier, but there cannot be multiple identifiers for a single profile. 2. Since the creation of the profile does not involve any CSR certification, it can be easily downloaded, installed, and accessed on any device.