Closed brooksr4 closed 11 months ago
@PaulKuykendall this is the DS data we talked about today. This should be moved up in priority and dealt refined async so it can be slotted for sooner rather than later. Can we add this to the top of priority for design?
For refinement: can we please separate the dev portion and the content/design portion into separate tickets? This will make it easier to track the progress and allow us to add points to each separately
Refinement Q: for ips epp accepts ip4 or ip6 as values when adding the ip to host. Should there be a dropdown with two values ip4/ip6 next to the ip address fields so a user can set which is applicable? Or just default to using ip6?
It'd be ideal to detect when a given address was (valid) v4 or v6, but in the absence of that having a user-selectable field defining the type would work.
Paul - research actual fields required, and think thru entire slice.
@PaulKuykendall Confused on this screencap of a drop down for Digest. On the Verisign screencap I see an open field for Digest, not a drop down.
@gabydisarli - My mistake. I mis-labeled that in the above reference. I've corrected it. that dropdown SHOULD have been under DS/DNS Data Algorithm.
added Figma design links. Figma designs are mostly done but small tweaks to copy here and there are happening in tandem with development
Name servers page is complete and linked in associated dev ticket. There is still one small copy change pending but marking this done as it's 99% there.
I will be making a new flow for DNSSEC without Keydata, that work is tracked in this ticket #1147
This ticket is an outcome of #817.
Story
As a Domain manager OR CISA Analyst/SuperUser I want to update all my DNS-related Data with the correct information so that my website/infrastructure is correctly linked to my .gov domain
Requirements
Digest Type - A DropDown Selector with a list of cryptographic hash algorithms, from a configurable file. (examples are SHA-1 or SHA-256![image](https://github.com/cisagov/getgov/assets/62573986/145766c8-d673-4af1-ad5e-f3f7dc19f457)
Digest - A text field to hold a cryptographic hash value of the referenced DNSKEY-record.
[x] DNSKey Data fields: The DNSKEY record contains the public signing key.
Constraints
DNS HOSTS:
Validations
Acceptance Criteria
[x] Domain Management page (/domain/{nn}/nameservers) includes fields for primary, secondary and additional host names and IPs
[x] Fields are available for DS Data and DNS Data: Key Tag, Algorithm, Digest Type, Digest
Additional Context
This is based on the following screenshot from the Verisign system: https://drive.google.com/file/d/1CkXnRQTcUHTD3lnfnk8VmrsMZV_4UzDy/view?usp=sharing
This affects page: /domain/{xxx}/nameservers, linked in big picture here:
Issue Links
🔄 Relates to: #817 Blocks: #1016 Figma designs
Clarifying Requirements in Slack Thread: https://cisa-corp.slack.com/archives/C05BDEA3C11/p1694524933555419