Skip to content

Conversation

@ajfarkas
Copy link
Contributor

Dev-Docs #11

Make sure that all instances of "Partner Portal" are capitalized, and other general instances of "portal" are lowercase.

@ajfarkas ajfarkas self-assigned this Dec 15, 2025
The <a target="_blank" href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/form-action">CSP form-action</a> directive restricts which URLs can be used as the target of form submissions from a given context. Certain Chromium-based internet browsers (e.g. Google Chrome and Microsoft Edge) enforce the form-action directive through the entire redirect chain (if any). Other non-Chromium-based browsers only check the first redirect in the chain (e.g. Firefox). For Chromium-based browsers, upon form submission, any attempts to redirect to a url not explicitly listed as a form-action source will violate the CSP directive and cause a failure to load and a console error.
<br/><br/>
This error occurs when Service Providers attempt to redirect users to a url that is not registered in the Redirect URLs field in the <a target="_blank" href="https://dashboard.int.identitysandbox.gov/">Login.gov Portal</a> application's configuration. All urls that users could be redirected to, even as a passthrough, need to be included in the list of Redirect URLs.
This error occurs when Service Providers attempt to redirect users to a url that is not registered in the Redirect URLs field in the <a target="_blank" href="https://dashboard.int.identitysandbox.gov/">Login.gov portal</a> application's configuration. All urls that users could be redirected to, even as a passthrough, need to be included in the list of Redirect URLs.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Question: outside of the scope of this ticket, but "Login.gov portal" seems... wrong, and it looks like we keep using that in various places. Some of these instances should probably be renamed to "Partner Portal", and others may need to be rephrased. @nickttng thoughts?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mmagsa Agreed - "Login.gov portal" looks wrong. In this case it should be either:

  • "Redirect URLs field in the Login.gov Partner Portal ..."
  • "Redirect URLs field in the portal ..."

Based on our content guidelines, it should be either "Partner Portal" (When needing to be formal) or "portal" (When it's okay to be informal).

Copy link
Contributor Author

@ajfarkas ajfarkas Dec 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is pretty small, there are 6 instances across 3 pages. Should we go with Partner Portal, since the original is somewhat formal, as "Login.gov portal"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will say there is at least one spot where "Login.gov Partner Portal" makes sense because it is in context with other portals (ie, 'MS Power Apps Portal')

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, check out the new commit. I can always roll it back or edit it further.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Partner Portal" as a standalone makes sense when it's clear on what it's talking about 👍🏼

Copy link
Contributor

@nickttng nickttng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The newer commits look good to me.

@ajfarkas ajfarkas merged commit 228d508 into main Dec 16, 2025
5 of 6 checks passed
@ajfarkas ajfarkas deleted the aj/dev-docs-11_capitalize-partner-portal branch December 16, 2025 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants