Join Log in
Score:0
Tomer Amir avatar Server

domain ownership verification in OIDC

cn flag
Tomer Amir

I am building an application where we want to allow our users to sign in using their own IDPs, and we're using okta.

We don't want our users to have to:

  • Create all their organization users manually
  • Be dependent on SCIM (or any other synchronization)
  • Maintain many users that most of them will probably not use our system

Since our user ids are email addresses and all of our customers are enterprises, we want to map domains to IDPs.

Meaning that if example.com is a customer of ours, then all email addresses like [email protected] or [email protected] should be handled by their IDP. the thing is we want to make sure that they own the domain example.com before adding their IDP to our discovery logic.

We were thinking about doing a DNS validation using a TXT record, but we aren't sure that this is the correct practice for this.

So finally my questions are:

  1. Is there a common practice for this?
  2. Are there downsides to the DNS record validation method?
  3. Are there any caveats we should be aware of? should we re-validate the ownership periodically?
22
0 + 0
ธงชาติไทย
Elon Musk
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.