application configuration → integration configuration

Author: Jeremy1026

_data/errors.yml

@@ -11,7 +11,7 @@ oidc:
         ##### What to do:
         - Ensure the authentication request has a `client_id` value
         - Ensure that the `client_id` sent in the authentication request matches the Issuer registered in your application's configuration on the [Partner Portal](https://portal.int.identitysandbox.gov/){:target="_blank"}.
-        - Ensure that the application configuration's "Accessible" setting is set to "Yes".
+        - Ensure that the integration configuration's "Accessible" setting is set to "Yes".
         - See our video [How to Troubleshoot and Fix "Bad client_id" Error for OIDC Integrations](https://www.youtube.com/watch?v=MAgSnjp1aOE) for a detailed visual explanation.
     - title: Missing a valid IAL level
       id: oidc-missing-ial
@@ -104,7 +104,7 @@ oidc:
         ##### What to do:
         - Ensure the logout request has a `client_id` value.
         - Ensure that the `client_id` sent in the logout request matches the one registered in your application on the [Partner Portal](https://dashboard.int.identitysandbox.gov/){:target="_blank"}.
-        - Ensure that the application configuration's `active` value is set to `true`.
+        - Ensure that the integration configuration's `active` value is set to `true`.
     - title: client_id is missing
       id: client-id-missing
       accordion-id: client_id_missing

_includes/support/faq_csp_violation.html

@@ -8,5 +8,5 @@ <h5>Background:</h5>
 </p>
 <h5>Solution:</h5>
 <p>
-    Use the Network tab of your web browser to identify which redirect (302) is hanging or failing. Add that uri to the list of Redirect URIs in your Login.gov Portal application configuration.
+    Use the Network tab of your web browser to identify which redirect (302) is hanging or failing. Add that uri to the list of Redirect URIs in your Login.gov Portal integration configuration.
 </p>

_includes/support/faq_unauthorized_sp.html

@@ -10,11 +10,11 @@ <h5>Solution:</h5>
 <p>
   <ul>
     <li>Double check your SAML request to Login.gov and confirm that the Issuer field matches exactly what is defined in the Login.gov <a href="https://portal.int.identitysandbox.gov/" class="usa-link">Partner Portal</a>.</li>
-    <li>Ensure that the application configuration’s "Accessible" setting is set to "Yes".</li>
+    <li>Ensure that the integration configuration’s "Accessible" setting is set to "Yes".</li>
     <li>See our video <a href="https://www.youtube.com/watch?v=SzTRc_c_5I4" class="usa-link">How to Troubleshoot and Fix "Unauthorized Service Provider" Error for SAML Integrations</a> for a detailed visual explanation.</li>
   </ul>
 
-  Note that certain Service Providers will not allow partners to set or change the Issuer value after the application is configured (e.g. MS Power Apps Portal). In this case, the best option would be to create the Login.gov Portal application configuration after the Service Provider application has defined the Issuer and use that Issuer in the Portal.
+  Note that certain Service Providers will not allow partners to set or change the Issuer value after the application is configured (e.g. MS Power Apps Portal). In this case, the best option would be to create the Login.gov Portal integration configuration after the Service Provider application has defined the Issuer and use that Issuer in the Portal.
 </p>
 
 <!-- markdown has to be formatted left-aligned -->

_pages/oidc/token.md

@@ -23,7 +23,7 @@ sidenav:
 
 ---
 {% capture client_assertion %}
-A [JWT](https://jwt.io/){:class="usa-link--external"} signed with the client’s private key (minimum length of 2048 bits) associated with the public key uploaded to your application configuration within the Portal. The JWT should use the RS256 algorithm and containing the following claims:
+A [JWT](https://jwt.io/){:class="usa-link--external"} signed with the client’s private key (minimum length of 2048 bits) associated with the public key uploaded to your integration configuration within the Portal. The JWT should use the RS256 algorithm and containing the following claims:
 - **iss** (string) — The issuer, which must be the `client_id`.
 - **sub** (string) — The subject, which must also be the `client_id`.
 - **aud** (string) — The audience, which should be (or, in the case of multiple audience values, include) the URL of the token endpoint, for example: `https://idp.int.identitysandbox.gov/api/openid_connect/token`

_pages/oidc/token/pkce.md

@@ -23,7 +23,7 @@ sidenav:
 
 ---
 {% capture client_assertion %}
-A [JWT](https://jwt.io/){:class="usa-link--external"} signed with the client’s private key (minimum length of 2048 bits) associated with the public key uploaded to your application configuration within the Dashboard. The JWT should use the RS256 algorithm and containing the following claims:
+A [JWT](https://jwt.io/){:class="usa-link--external"} signed with the client’s private key (minimum length of 2048 bits) associated with the public key uploaded to your integration configuration within the Dashboard. The JWT should use the RS256 algorithm and containing the following claims:
 - **iss** (string) — The issuer, which must be the `client_id`.
 - **sub** (string) — The subject, which must also be the `client_id`.
 - **aud** (string) — The audience, which should be (or, in the case of multiple audience values, include) the URL of the token endpoint, for example: `https://idp.int.identitysandbox.gov/api/openid_connect/token`

_pages/production.md

@@ -35,7 +35,7 @@ Make sure you have the following items ready before you start the deployment pro
 
 -   [Signed Interagency Agreement (IAA) listing this integration ]({{ site.baseurl}}/production/#confirm-interagency-agreement-iaa)
 
--   A dedicated [application configuration within the Portal](https://dashboard.int.identitysandbox.gov/)
+-   A dedicated [integration configuration within the Portal](https://dashboard.int.identitysandbox.gov/)
     * We recommend having two configurations, one that is intended for deployment to production and one which is purely for testing purposes.
     * All production urls should have .gov, .mil, or a dedicated .com address and point to an Authority to Operate (ATO) approved environment.
 
@@ -69,13 +69,13 @@ Please reach out to your agency IAA contact if you have any questions. If your a
 
 ## Production configuration process
 
-Before you can request deployment, you need to create a new and separate application configuration on our partner portal. This new app will include your production certificate, urls, and logo. When starting this process you need the following items ready to go:
+Before you can request deployment, you need to create a new and separate integration configuration on our partner portal. This new app will include your production certificate, urls, and logo. When starting this process you need the following items ready to go:
 
 -   Signed IAA listing this integration 
 -   ATO approved environment
 -   [Approved agency logo](/user-experience/agency-logo/) for your app
 
-When you have the components required, follow these steps to create your production application configuration:
+When you have the components required, follow these steps to create your production integration configuration:
 
 1.  [Create a new app on the](https://dashboard.int.identitysandbox.gov/) Login.gov Partner Portal. Select “Apps” from the top right menu, then select the “Create a new app” button.
 
@@ -155,7 +155,7 @@ We recommend using the sandbox environment to test your new app before requestin
 
 **Changes to production configurations are not automatic and may take up to two weeks.**
 
-If you need to make any changes to your deployed integration, please update your production application configuration in the sandbox and test the changes you wish to deploy. After you have confirmed the change, **you must submit a change request** through the [Partner Support Help Desk](https://zendesk.login.gov) to ensure the change takes effect in production.
+If you need to make any changes to your deployed integration, please update your production integration configuration in the sandbox and test the changes you wish to deploy. After you have confirmed the change, **you must submit a change request** through the [Partner Support Help Desk](https://zendesk.login.gov) to ensure the change takes effect in production.
 
 ### Certificate Rotation Process
 

_pages/testing.md

@@ -51,7 +51,7 @@ Please submit a support ticket through the [Partner Support Help Desk](https://z
 1. If you already have a Login.gov test account, select the “Sign in” button in the upper-right corner to sign in.
 1. You must create a team before you can create a new app. Create a new team by selecting the “Continue” button under “Create your first team.” If you have previously created a team you can move on to the next step.
 1. If necessary, add users to that team by clicking the “Add users” button. This is the opportunity to add contractors or anyone without a .gov or a .mil email address.
-1. After creating your team, select the Apps tab. This page is where you will find all of the application configurations you and your team create.
+1. After creating your team, select the Apps tab. This page is where you will find all of the integration configurations you and your team create.
 1. Select the “Create a new app” button and follow the steps to register a new application with the Login.gov IdP in the test sandbox environment. You can only have one app creation in progress at a time. There are links to additional information throughout the form. We recommend reading through the descriptions carefully.
 1. To troubleshoot specific errors, please visit our error dictionary in the [troubleshooting section of our developer documentation]({% link _pages/support.md %}). If the guidance there does not resolve the error, please submit a support ticket through the [Partner Support Help Desk](https://zendesk.login.gov/).
 1. Start testing!
@@ -62,7 +62,7 @@ Please submit a support ticket through the [Partner Support Help Desk](https://z
 Login.gov does not manage user accounts. If you have lost access to a team:
 * Request someone on your team who still has access to re-add you.
 * If there is no one left with access, contact the partner agency's Login.gov Point of Contact and request that they re-add you to the team.
-* If they are unable to re-add you, request that they open up a ticket through the [Partner Support Help Desk](https://zendesk.login.gov) explaining the situation and confirming that you need access. They must include either the issuer or the link to the application configuration.
+* If they are unable to re-add you, request that they open up a ticket through the [Partner Support Help Desk](https://zendesk.login.gov) explaining the situation and confirming that you need access. They must include either the issuer or the link to the integration configuration.
 
 ### Creating a public certificate