zydronium/manage.get.gov
1
0
Fork 0
mirror of https://github.com/cisagov/manage.get.gov.git synced 2025-05-21 11:59:24 +02:00
Code Issues Projects Releases Packages Wiki Activity

Find-replace "domain application", "domain_application", "domain-application" with "domain request", "domain_request", "domain-request". Preserved camel-cases through strict find-replace conditions.

Browse source
This commit is contained in:
CocoByte 2024-02-29 14:11:43 -07:00
parent b355f1813d
commit 0ce03d21c7
No known key found for this signature in database
GPG key ID: BBFAA2526384C97F
80 changed files with 721 additions and 721 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/architecture/decisions/0022-submit-domain-request-user-flow.md
View file

@ -8,7 +8,7 @@ Accepted
## Context
Historically, the .gov vendor managed initial identity verification and organizational affiliation for users that request a .gov domain. With the new registrar, _any user with a valid Login.gov account_ will be able to make a request. As a primary layer of abuse prevention (i.e., DDoSing the registry program with illegitimate requests), we need a way to stop new users from submitting multiple domain requests before they are known to the .gov registry. In this case, "known" means they have at least one approved domain application or existing domain.
Historically, the .gov vendor managed initial identity verification and organizational affiliation for users that request a .gov domain. With the new registrar, _any user with a valid Login.gov account_ will be able to make a request. As a primary layer of abuse prevention (i.e., DDoSing the registry program with illegitimate requests), we need a way to stop new users from submitting multiple domain requests before they are known to the .gov registry. In this case, "known" means they have at least one approved domain request or existing domain.
## Considered Options