From 726d6eb06629011be9381644a364231f9966cd4d Mon Sep 17 00:00:00 2001 From: rahul-kamarouthu Date: Tue, 5 Nov 2024 14:58:08 -0500 Subject: [PATCH 1/5] LG-14519 Change Dashboard to Portal --- _layouts/base.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_layouts/base.html b/_layouts/base.html index 4d1923af..5156047c 100644 --- a/_layouts/base.html +++ b/_layouts/base.html @@ -120,14 +120,14 @@

From 59b3c6a252cd2ad98c04034ca29f6d9c9bdab012 Mon Sep 17 00:00:00 2001 From: rahul-kamarouthu Date: Wed, 6 Nov 2024 09:35:30 -0500 Subject: [PATCH 2/5] Update dev docs dashboard to portal --- _data/errors.yml | 12 +++++------ _pages/index.md | 4 ++-- _pages/oidc/getting-started.md | 2 +- _pages/oidc/token.md | 2 +- _pages/production.md | 14 ++++++------ _pages/saml/getting-started.md | 2 +- _pages/security-events.md | 2 +- _pages/support.md | 26 +++++++++++------------ _pages/testing.md | 8 +++---- _pages/user-experience/agency-logo.md | 2 +- _pages/user-experience/getting-started.md | 6 +++--- 11 files changed, 40 insertions(+), 40 deletions(-) diff --git a/_data/errors.yml b/_data/errors.yml index 91d68db8..c24fb9ea 100644 --- a/_data/errors.yml +++ b/_data/errors.yml @@ -8,7 +8,7 @@ oidc: The issuer (also known as the client id) provided does not match a service provider registered in the IdP. ##### What to do: - Ensure the authentication request has a `client_id` value - - Ensure that the `client_id` sent in the authentication request matches the one registered in your application on the [Partner Dashboard](https://dashboard.int.identitysandbox.gov/){:target="_blank"}. + - Ensure that the `client_id` sent in the authentication 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`. - title: Missing a valid IAL level id: oidc-missing-ial @@ -31,7 +31,7 @@ oidc: If your application is Authentication Only, check the value of your `acr_values` parameter and ensure that it does **not** include `http://idmanagement.gov/ns/assurance/ial/2`. If you believe your application **SHOULD** be set to Identity Verification Permitted, please: - Reach out to your account manager to make sure your application is authorized for IdV. If it isn't, they can work with you to determine the right service level for your application. - - If your application **is** authorized for IdV, go to the dashboard and update the Level of Service value to "Identity Verification Permitted." + - If your application **is** authorized for IdV, go to the portal and update the Level of Service value to "Identity Verification Permitted." - If this is a production instance, submit a [Zendesk request](https://zendesk.login.gov){:target="_blank"} to deploy that change to production. - title: No acceptable acr_values found id: oidc-no-acr-values @@ -70,7 +70,7 @@ oidc: ##### Why it's happening You have registered a redirect URI that cannot be parsed. ##### What to do: - - Check your application's configuration on the [Partner Dashboard](https://dashboard.int.identitysandbox.gov/){:target="_blank"}. + - Check your application's configuration on the [Partner Portal](https://dashboard.int.identitysandbox.gov/){:target="_blank"}. - Ensure that all registered redirect_uris are propertly formatted and use `https` protocol. - title: redirect_uri does not match registered redirect_uri id: oidc-redirect-match @@ -79,7 +79,7 @@ oidc: ##### Why it's happening You have not registered the redirect_uri that you sent in your authentication request. ##### What to do: - - Check your application's configuration on the [Partner Dashboard](https://dashboard.int.identitysandbox.gov/){:target="_blank"} and the `redirect_uri` passed through your authentication request. + - Check your application's configuration on the [Partner Portal](https://dashboard.int.identitysandbox.gov/){:target="_blank"} and the `redirect_uri` passed through your authentication request. - Ensure the `redirect_uri` that you are sending as part of your authentication request is registered. You must register every redirect uri that your application redirects through. - title: Unauthorized scope id: oidc-unauthotized-scope @@ -100,7 +100,7 @@ oidc: The issuer (also known as the client id) provided does not match a service provider registered in the IdP. ##### 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 Dashboard](https://dashboard.int.identitysandbox.gov/){:target="_blank"}. + - 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`. - title: client_id is missing id: client-id-missing @@ -194,7 +194,7 @@ oidc: ##### Why it's happening There is no registered certificate that matches the signature of the `client_assertion` JWT that is being passed as part of the token. request. ##### What to do: - - Ensure that the public certificate that matches the private key used to sign the JWT is registered in your application's configuration in the [Partner Dashboard](https://dashboard.int.identitysandbox.gov/){:target="_blank"}. + - Ensure that the public certificate that matches the private key used to sign the JWT is registered in your application's configuration in the [Partner Portal](https://dashboard.int.identitysandbox.gov/){:target="_blank"}. userinfo: - title: Malformed Authorization header id: malformed-auth-header diff --git a/_pages/index.md b/_pages/index.md index e9d7e3d4..e88ba83f 100644 --- a/_pages/index.md +++ b/_pages/index.md @@ -17,7 +17,7 @@ layout: home

  1. - Your integration with Login.gov starts in the dashboard where you can register your app. + Your integration with Login.gov starts in the portal where you can register your app.

  2. @@ -32,7 +32,7 @@ layout: home

  3. - Configure your app in the dashboard and start testing! We have implementation guides and example apps to get you up and running quickly. + Configure your app in the portal and start testing! We have implementation guides and example apps to get you up and running quickly.

  4. diff --git a/_pages/oidc/getting-started.md b/_pages/oidc/getting-started.md index 81e5edab..4460055c 100644 --- a/_pages/oidc/getting-started.md +++ b/_pages/oidc/getting-started.md @@ -56,7 +56,7 @@ The following implementation methods of OIDC are not supported by Login.gov for ### Set up a Sandbox account -You are able to test authentication methods in real time with a testing account in our sandbox environment. To start, navigate to the [Login Partner Dashboard Sandbox](https://dashboard.int.identitysandbox.gov) and follow the steps below: +You are able to test authentication methods in real time with a testing account in our sandbox environment. To start, navigate to the [Login Partner Portal Sandbox](https://dashboard.int.identitysandbox.gov) and follow the steps below: - Select the “Sign-in” button to create a new account. Anyone with a .gov or .mil email address may request an account. - Create a new team - see [Testing](/testing/) page for instructions. diff --git a/_pages/oidc/token.md b/_pages/oidc/token.md index bfe38b7b..b250c87e 100644 --- a/_pages/oidc/token.md +++ b/_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 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 application 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` diff --git a/_pages/production.md b/_pages/production.md index 9d384436..1132c837 100644 --- a/_pages/production.md +++ b/_pages/production.md @@ -1,7 +1,7 @@ --- title: Production deployment lead: > - Once you’ve set up your integration through [our dashboard](https://dashboard.int.identitysandbox.gov/) and tested, you can request deployment to the Login.gov production environment. + Once you’ve set up your integration through [our portal](https://dashboard.int.identitysandbox.gov/) and tested, you can request deployment to the Login.gov production environment. redirect_from: - /production-deployment/ @@ -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 Dashboard](https://dashboard.int.identitysandbox.gov/) +- A dedicated [application 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,7 +69,7 @@ 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 on our dashboard. 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 application on our 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  @@ -79,7 +79,7 @@ Before you can request deployment, you need to create a new and separate applica **When you have the components required, follow these steps to create your production configuration app:** -1. [Create a new app on the](https://dashboard.int.identitysandbox.gov/) Login.gov Partner Dashboard. Select “Apps” from the top right menu, then select the “Create a new app” button. +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. 2. Select “YES” for production configuration - this configuration is for a production app. @@ -131,7 +131,7 @@ Once you have: 2. [Created a production configuration app]({{site.baseurl}}/production/#production-configuration-process). -3. Confirmed that you have a logo uploaded to your production configuration in the [Partner Dashboard](https://dashboard.int.identitysandbox.gov/). **An uploaded logo is required for the deployment process.** +3. Confirmed that you have a logo uploaded to your production configuration in the [Partner Portal](https://dashboard.int.identitysandbox.gov/). **An uploaded logo is required for the deployment process.** You are ready to submit a launch request through the [Partner Support Help Desk](https://zendesk.login.gov).  @@ -161,7 +161,7 @@ If you are rotating your application’s public/private keypair, or want to add **For OIDC integrations or SAML integrations sending signed requests:** - 1. Add the new certificate to the application dashboard configuration. + 1. Add the new certificate to the application portal configuration. 2. Contact Login.gov technical support and request certificate addition. @@ -174,7 +174,7 @@ If you are rotating your application’s public/private keypair, or want to add 1. The final certificate rotation must be coordinated with Login.gov technical support. - 2. Add the new certificate to the application dashboard configuration. + 2. Add the new certificate to the application portal configuration. 3. Request coordination of the certificate rotation from Login.gov technical support. diff --git a/_pages/saml/getting-started.md b/_pages/saml/getting-started.md index f169a421..0a44a634 100644 --- a/_pages/saml/getting-started.md +++ b/_pages/saml/getting-started.md @@ -94,7 +94,7 @@ Here are values needed to configure your service provider (SP) to work with Logi Consistent with the [SAML metadata specification](https://docs.oasis-open.org/security/saml/v2.0/saml-metadata-2.0-os.pdf){:class="usa-link--external"}, Login.gov's metadata for our sandbox environment is available at [https://idp.int.identitysandbox.gov/api/saml/metadata{{ site.data.saml.year.current }}](https://idp.int.identitysandbox.gov/api/saml/metadata{{ site.data.saml.year.current }}). ### Signing Certificates -Below you can find the X509 certificates used by the Login.gov IdP to sign SAML requests. **Do not enter these certificates in the Dashboard when configuring an application for testing** - you can follow the instructions in our [testing article]({% link _pages/testing.md %}#creating-a-public-certificate) to generate a client certificate. +Below you can find the X509 certificates used by the Login.gov IdP to sign SAML requests. **Do not enter these certificates in the Portal when configuring an application for testing** - you can follow the instructions in our [testing article]({% link _pages/testing.md %}#creating-a-public-certificate) to generate a client certificate.
    Check validity of signature

    - There may be other reasons Login.gov cannot successfully validate your application’s signatures using the information you have provided in the Login.gov Partner Dashboard for the application. We have created a web-based tool that lets you check this easily. + There may be other reasons Login.gov cannot successfully validate your application’s signatures using the information you have provided in the Login.gov Partner Portal for the application. We have created a web-based tool that lets you check this easily.

    If you find your signature cannot be validated using this process, you will have to investigate what may be causing these problems and make changes on your side until validation succeeds.

    @@ -494,7 +494,7 @@ If you prefer using Slack, we have a slack channel for partners, **#login-partne Before submitting your Zendesk ticket, please review the developer documentation on our website. Often the answers we will provide can be found there. When submitting a Zendesk ticket, particularly in cases when you are encountering an error, you can minimize your time to resolve the issue by providing the following information: - * Link to your dashboard configuration + * Link to your portal configuration * Screenshots of all error messages * What browser you were using * Time the error(s) occurred or if it is ongoing @@ -514,7 +514,7 @@ Here is a list of common issues partners encounter that our team can assist with * Authentication failures while testing in sandbox environment * Questions about OIDC/SAML protocols -* Problems with dashboard configuration (configuration not updating as expected) +* Problems with portal configuration (configuration not updating as expected) * Invalid PIV/CAC certificate errors (we may need to update certs on our end) * Problems updating or deploying a production configuration * Clarification about something in our developer docs @@ -523,8 +523,8 @@ Here is a list of common issues partners encounter that our team can assist with * Troubles with redirecting back to your application / Service Provider * Trouble reading or receiving expected user attributes * Users being unable to sign into production Service Provider (these are top priority to resolve, assuming it is related to Login.gov) -* Feedback you want to share about your experience using the developer docs / dashboard (we are always looking to improve) -* Any bugs you encounter in the dashboard or developer docs (broken links, user management issues, etc) +* Feedback you want to share about your experience using the developer docs / portal (we are always looking to improve) +* Any bugs you encounter in the portal or developer docs (broken links, user management issues, etc)
    @@ -543,7 +543,7 @@ There are some cases where our team is unable to help, typically either for secu * Debugging network connection issues (if the connection isn’t going through, we cannot see it on our end and thus have very limited ability to troubleshoot) * Any kind of PII request (we do not give out PII for any reason) * Debugging your internal server setup (we can try to direct you to documentation but our server knowledge is limited) -* Providing access to the dashboard (for security purposes, the dashboard is self service and anyone with a .gov / .mil address can provide access - [View Product Deployment for further instructions](https://developers.login.gov/production/#before-deployment)) +* Providing access to the portal (for security purposes, the portal is self service and anyone with a .gov / .mil address can provide access - [View Product Deployment for further instructions](https://developers.login.gov/production/#before-deployment)) * You’ve found a vulnerability and want to report it (Instead, please submit through [Login.gov Security Vulnerability Disclosure](https://docs.google.com/forms/d/e/1FAIpQLScuo4xCzBlpLnoq7-bDAVAxtJci03by7S-Q-Z_JUBDloK01QA/viewform)) diff --git a/_pages/testing.md b/_pages/testing.md index 1078eedd..50ad049f 100644 --- a/_pages/testing.md +++ b/_pages/testing.md @@ -1,7 +1,7 @@ --- title: Testing your app lead: > - Once you’ve created your app and implemented an identity protocol, you can now register it in the test environment dashboard and start testing. + Once you’ve created your app and implemented an identity protocol, you can now register it in the test environment portal and start testing. redirect_from: - /registering-your-sp/ - /register/ @@ -27,7 +27,7 @@ sidenav: Login.gov provides an open sandbox environment to create and test integrations between Login.gov and your applications. **Note that the Login.gov Sandbox environment is a free service with an availability target of M-F, 8a-5p ET.** While it is typically online within that window, there are occasional hiccups that should resolve quickly on their own. The environment may at times be available outside of this window, but it is not guaranteed and may become unavailable with no advance notice. -In the sandbox environment, our [Dashboard](https://dashboard.int.identitysandbox.gov) is where you can manage your test applications. ***It is important to note that your Login.gov production account and your Login.gov sandbox account are two separate accounts.*** +In the sandbox environment, our [Portal](https://dashboard.int.identitysandbox.gov) is where you can manage your test applications. ***It is important to note that your Login.gov production account and your Login.gov sandbox account are two separate accounts.*** ## Getting access to the Login.gov sandbox @@ -40,11 +40,11 @@ You can create an account in the sandbox environment on your own. Ask your agency partner to help you gain access. Login.gov will not create an account or add you to a team; your partner must do this for you. **If you are with a government entity that is not a federal agency (a state or municipality) and do not have an email ending in .gov or .mil** -Please submit a support ticket through the [Partner Support Help Desk](https://zendesk.login.gov) to get access to the Dashboard. +Please submit a support ticket through the [Partner Support Help Desk](https://zendesk.login.gov) to get access to the Portal. ## Using the sandbox -1. Visit the Partner Dashboard at [https://dashboard.int.identitysandbox.gov](https://dashboard.int.identitysandbox.gov). +1. Visit the Partner Portal at [https://dashboard.int.identitysandbox.gov](https://dashboard.int.identitysandbox.gov). 1. Select the “Sign in” button in the upper-right corner to sign in or create a new account with the test Login.gov IdP in the sandbox environment hosted at [idp.int.identitysandbox.gov](https://idp.int.identitysandbox.gov). **Please note that this is separate from your Login.gov production account.** 1. Once you are logged into your sandbox account, create a new team by selecting the “Continue” button under “Create your first team." (If you have previously created a team you will select the “Create a new team” button.) 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** diff --git a/_pages/user-experience/agency-logo.md b/_pages/user-experience/agency-logo.md index 1bfca60e..57d46511 100644 --- a/_pages/user-experience/agency-logo.md +++ b/_pages/user-experience/agency-logo.md @@ -27,7 +27,7 @@ sidenav: ## Add your agency logo -All applications are required to add a logo, which is uploaded in the Partner Dashboard. +All applications are required to add a logo, which is uploaded in the Partner Portal. Your agency logo will appear to the right of the Login.gov logo in your integration. This helps to ensure users understand the partnership between Login.gov and your integration with our service. diff --git a/_pages/user-experience/getting-started.md b/_pages/user-experience/getting-started.md index 9457f068..6de4e900 100644 --- a/_pages/user-experience/getting-started.md +++ b/_pages/user-experience/getting-started.md @@ -26,14 +26,14 @@ sidenav: --- ## Getting started -There are several decisions during the integration process that affect how your users experience Login.gov. In this User Experience guide, we will outline what options you have available to your application, and the configurations in Login.gov [dashboard](https://dashboard.int.identitysandbox.gov/) that impact users. +There are several decisions during the integration process that affect how your users experience Login.gov. In this User Experience guide, we will outline what options you have available to your application, and the configurations in Login.gov [portal](https://dashboard.int.identitysandbox.gov/) that impact users. {% capture button_ux %} [Design your application's sign-in and sign-out buttons]({{site.baseurl}}/user-experience/sign-in-sign-out/). This will include a [global sign-in button]({{site.baseurl}}/user-experience/sign-in-sign-out/), and optionally, [a sign-in page]({{site.baseurl}}/user-experience/sign-in-sign-out/) before the user is directed to Login.gov. {% endcapture %} {% capture failure_to_proof_ux %} -All partners with identity verification will [create a Failure to Proof URL]({{site.baseurl}}/user-experience/failure-proof/) for users who cannot pass identity proofing with Login.gov. This URL is configured in the sandbox dashboard, but may require designing a new page or process on your agency's website or application. +All partners with identity verification will [create a Failure to Proof URL]({{site.baseurl}}/user-experience/failure-proof/) for users who cannot pass identity proofing with Login.gov. This URL is configured in the sandbox portal, but may require designing a new page or process on your agency's website or application. {% endcapture %} {% capture link_to_helpdesk %} @@ -74,7 +74,7 @@ Optional: [Add FAQ content to inform users about Login.gov]({{site.baseurl}}/use
    5. -### Configure in the [dashboard](https://dashboard.int.identitysandbox.gov/) +### Configure in the [portal](https://dashboard.int.identitysandbox.gov/)
    • From 572c7f94559b5e17f521f67cd777286290a39c42 Mon Sep 17 00:00:00 2001 From: rahul-kamarouthu Date: Fri, 8 Nov 2024 09:04:37 -0500 Subject: [PATCH 3/5] Changed one instance of dashboard to portal --- _pages/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_pages/overview.md b/_pages/overview.md index a4911721..273db4d8 100644 --- a/_pages/overview.md +++ b/_pages/overview.md @@ -28,7 +28,7 @@ Login.gov is a FedRAMP moderate approved multifactor authentication and identity This is the configuration for your application within Login.gov’s identity provider. In the sandbox environment, you will be able to determine the configuration yourself and decide what is the best fit for your needs. In the Login.gov production environment, we will manage the final configuration. To configure a test application in the sandbox environment: -* Create an account in the [Login.gov dashboard](https://idp.int.identitysandbox.gov/). From here you will be able to test various configurations and determine what is right for your agency. +* Create an account in the [Login.gov portal](https://idp.int.identitysandbox.gov/). From here you will be able to test various configurations and determine what is right for your agency. * Select between [OIDC]({{ site.baseurl }}/oidc/) or [SAML]({{ site.baseurl }}/saml/) protocol implementation protocols and understand which user attributes are required. * If you have questions when testing your app, read through our [FAQs]({{ site.baseurl }}/support/) or submit a ticket to our [technical support help desk]({{ site.baseurl}}/support/#contacting-partner-support). * Before submitting a request to move your app to production, review the [User experience]({{ site.baseurl }}/design-guidelines/) page and the [Production]({{ site.baseurl }}/production/) page. Additional requirements, like a [signed Interagency agreement]({{ site.baseurl }}/production/#confirm-interagency-agreement-iaa) (IAA) and [agency logo]({{ site.baseurl }}/user-experience/agency-logo/), are described in these pages. From a5a1b034e6da5e6d31bed5fb15f34326bd03c554 Mon Sep 17 00:00:00 2001 From: rahul-kamarouthu Date: Tue, 12 Nov 2024 11:17:37 -0500 Subject: [PATCH 4/5] Updated dashboard link to reflect portal --- _pages/overview.md | 2 +- _pages/testing.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/_pages/overview.md b/_pages/overview.md index 273db4d8..9eafb59d 100644 --- a/_pages/overview.md +++ b/_pages/overview.md @@ -28,7 +28,7 @@ Login.gov is a FedRAMP moderate approved multifactor authentication and identity This is the configuration for your application within Login.gov’s identity provider. In the sandbox environment, you will be able to determine the configuration yourself and decide what is the best fit for your needs. In the Login.gov production environment, we will manage the final configuration. To configure a test application in the sandbox environment: -* Create an account in the [Login.gov portal](https://idp.int.identitysandbox.gov/). From here you will be able to test various configurations and determine what is right for your agency. +* Create an account in the [Login.gov Portal](portal.int.identitysandbox.gov). From here you will be able to test various configurations and determine what is right for your agency. * Select between [OIDC]({{ site.baseurl }}/oidc/) or [SAML]({{ site.baseurl }}/saml/) protocol implementation protocols and understand which user attributes are required. * If you have questions when testing your app, read through our [FAQs]({{ site.baseurl }}/support/) or submit a ticket to our [technical support help desk]({{ site.baseurl}}/support/#contacting-partner-support). * Before submitting a request to move your app to production, review the [User experience]({{ site.baseurl }}/design-guidelines/) page and the [Production]({{ site.baseurl }}/production/) page. Additional requirements, like a [signed Interagency agreement]({{ site.baseurl }}/production/#confirm-interagency-agreement-iaa) (IAA) and [agency logo]({{ site.baseurl }}/user-experience/agency-logo/), are described in these pages. diff --git a/_pages/testing.md b/_pages/testing.md index 50ad049f..6b2852cd 100644 --- a/_pages/testing.md +++ b/_pages/testing.md @@ -44,7 +44,7 @@ Please submit a support ticket through the [Partner Support Help Desk](https://z ## Using the sandbox -1. Visit the Partner Portal at [https://dashboard.int.identitysandbox.gov](https://dashboard.int.identitysandbox.gov). +1. Visit the Partner Portal at [portal.int.identitysandbox.gov](portal.int.identitysandbox.gov). 1. Select the “Sign in” button in the upper-right corner to sign in or create a new account with the test Login.gov IdP in the sandbox environment hosted at [idp.int.identitysandbox.gov](https://idp.int.identitysandbox.gov). **Please note that this is separate from your Login.gov production account.** 1. Once you are logged into your sandbox account, create a new team by selecting the “Continue” button under “Create your first team." (If you have previously created a team you will select the “Create a new team” button.) 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** From 7719d0fb84a98a8ece40e81baf44705eb81082d6 Mon Sep 17 00:00:00 2001 From: rahul-kamarouthu Date: Tue, 12 Nov 2024 15:57:10 -0500 Subject: [PATCH 5/5] Fixed missing https in urls --- _pages/overview.md | 2 +- _pages/testing.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/_pages/overview.md b/_pages/overview.md index 9eafb59d..68ae7831 100644 --- a/_pages/overview.md +++ b/_pages/overview.md @@ -28,7 +28,7 @@ Login.gov is a FedRAMP moderate approved multifactor authentication and identity This is the configuration for your application within Login.gov’s identity provider. In the sandbox environment, you will be able to determine the configuration yourself and decide what is the best fit for your needs. In the Login.gov production environment, we will manage the final configuration. To configure a test application in the sandbox environment: -* Create an account in the [Login.gov Portal](portal.int.identitysandbox.gov). From here you will be able to test various configurations and determine what is right for your agency. +* Create an account in the [Login.gov Portal](https://portal.int.identitysandbox.gov). From here you will be able to test various configurations and determine what is right for your agency. * Select between [OIDC]({{ site.baseurl }}/oidc/) or [SAML]({{ site.baseurl }}/saml/) protocol implementation protocols and understand which user attributes are required. * If you have questions when testing your app, read through our [FAQs]({{ site.baseurl }}/support/) or submit a ticket to our [technical support help desk]({{ site.baseurl}}/support/#contacting-partner-support). * Before submitting a request to move your app to production, review the [User experience]({{ site.baseurl }}/design-guidelines/) page and the [Production]({{ site.baseurl }}/production/) page. Additional requirements, like a [signed Interagency agreement]({{ site.baseurl }}/production/#confirm-interagency-agreement-iaa) (IAA) and [agency logo]({{ site.baseurl }}/user-experience/agency-logo/), are described in these pages. diff --git a/_pages/testing.md b/_pages/testing.md index 6b2852cd..030a0f4a 100644 --- a/_pages/testing.md +++ b/_pages/testing.md @@ -44,7 +44,7 @@ Please submit a support ticket through the [Partner Support Help Desk](https://z ## Using the sandbox -1. Visit the Partner Portal at [portal.int.identitysandbox.gov](portal.int.identitysandbox.gov). +1. Visit the Partner Portal at [portal.int.identitysandbox.gov](https://portal.int.identitysandbox.gov). 1. Select the “Sign in” button in the upper-right corner to sign in or create a new account with the test Login.gov IdP in the sandbox environment hosted at [idp.int.identitysandbox.gov](https://idp.int.identitysandbox.gov). **Please note that this is separate from your Login.gov production account.** 1. Once you are logged into your sandbox account, create a new team by selecting the “Continue” button under “Create your first team." (If you have previously created a team you will select the “Create a new team” button.) 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**