Configure IdP-Initiated SSO for Procore with Okta

If your company manages your users with Okta, you can leverage its SSO capabilities. This gives your end users the ability to authenticate their identify for the Procore application using their Okta account. With this SSO integration, you can:

• Leverage Okta for SSO access to Procore.

• Simplify your entire organization's password management process.

• Avoid problematic user password management.

• Authentication Protocol:

  • You can integrate the Procore application with Okta using the Security Assertion Markup Language (SAML 2.0).

• Requirements:

  • Okta

• Required Permissions:

  • Super Administrator rights to Okta.

  • 'Admin' level permissions to the Company Admin tool.

Step 1: Add the Procore Application to Okta

1. Log in to Okta as an Administrator.

2. Click Admin.
   
   
   

3. Choose Applications > Applications.
   
   
   

4. Click Add Application.
   
   
   
   

5. In the Search for an Application box, search for Procore. When Procore's Okta-Verified SAML app appears, click Add.
   
   
   

6. Under General Settings, do the following:

   • Application Label. Type a name for the new application. For example, type: Procore

   • Application Visibility. Leave both of these checkboxes blank. This will allow the Procore icon to appear in Okta and on the Okta login page. If you place a checkmark in this box, the logo with NOT appear.

   • Browser Plugin Auto-Submit. Ensure a checkmark appears in this box.
     
     

7. Click Next.
   
   
   

8. Click View Setup Instructions.
   This opens the Setup SSO page in a new web browser tab. Leave this page open in your browser. Later, you will need to copy information in this page when you configure the Okta SSO settings in the Procore web application.
   Important! When copying the X.509 Certificate string, do NOT copy the "------------BEGIN CERTIFICATE------------" and "------------END CERTIFICATE------------" markers. Only copy the text that resides between these markers.
   

9. Return to your open browser tab with Okta's Sign On page, as shown below. Then ensure that Okta Username is selected in the Application Username Format list.
   
   
   

10. Click Next.

11. Place a checkmark next to the name of your organization's Procore users in the People list.
    
    
    

12. Click Next.

13. Verify that the attribute settings are correct for all of your Procore users. This Otka username is an email address. This is the address that you Procore users will use to log in to your Procore + Okta SSO Integration.
    
    
    

14. Click Done.

15. Continue with the next procedure.

Step 2: Configure the Okta Settings in Procore

1. Login into the Procore web application.
   Note: You must log in using an account that has 'Admin' permission to the company's Admin tool.

2. Navigate to the company's Admin tool.

3. Under Administrative Settings, click Single Sign On Configuration.

4. Enter the following information:

   • Single Sign On Issuer URL
     Paste the 'Identity Provider Single Sign-On URL' that you copied from Okta into this field.

   • Single Sign On Target URL.
     Leave this field blank.

   • Single Sign On x509
     Paste the 'X509 Certificate' that you copied from Okta into this field.
     Important: When copying the certificate information from Okta, do NOT copy the "------------BEGIN CERTIFICATE------------" and "------------END CERTIFICATE------------" markers. You only want to copy the text that resides between these markers.
     
     
     

5. Click Save Changes.

6. Next, reach out to your company's Procore point of contact or contact Procore Support to request that they enter the domains you want to target for authentication via SSO. Procore must enter these domains on your behalf.

7. Once the domain(s) have been entered by Procore, take the final steps to enable SSO for your company:

   1. Mark the Enable Single Sign On box in Procore's SSO configuration settings.

   2. Select Allow Password Login to enable an IdP-initiated flow.

   3. Click Save.

Authentication via the configured SSO method will become active immediately after saving the final completed configuration.