We attempted three different ways to provide domain verification.
(PS: We have checked the instruction on the website: Cursor – SSO, but it does not work for us)
(PPS: We’ve sent the messages to [email protected] on June 18th, July 9th,… this year and haven’t received a response)
Creating a hostname with the verification string:
dig TXT cursor-domain-verification-npbhqy.ece.ufl.edu
Adding the text record to the domain ece.ufl.edu
$ dig TXT ece.ufl.edu
; <<>> DiG 9.11.36-RedHat-9.11.36-16.el8_10.4 <<>> TXT ece.ufl.edu
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37945
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 3, ADDITIONAL: 6
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1220
; COOKIE: 016706708937246d0100000068790e4559ceea52… (good)
;; QUESTION SECTION:
;ece.ufl.edu. IN TXT
;; ANSWER SECTION:
ece.ufl.edu. 3600 IN TXT “nengqCUhC+D2bgfj22KNH8PbStOhNzIfD0iHPDeX3SCcXgvpguKvOv2T4P1AnC+murwEpO…”
ece.ufl.edu. 3600 IN TXT “cursor-domain-verification-npbhqy=NoWWU…”
3) Because of the syntax shown on the domain screen, we created a dummy record
ece.ece.ufl.edu
with the text record: ece.ufl.edu. 3600 IN TXT "cursor-domain-verification-npbhqy=NoWWUQpDMTM..."
On our end, we were able to validate using dig.
Despite adding these three different DNS records, the verification of the domain never succeeded. The admin console just spun on verifying domain.
We need a little more detail on what we need to successfully pass the domain verification process, in order for us to move on to the SSO setup.