failed to obtain the Organization associated with jurisdicti

Error message

failed to obtain the Organization associated with jurisdiction %s and registration ID %s

What it means

FindOrgByJurisdictionAndRegistrationIDClaim found the registration_id Identifier but could not resolve an Organization whose jurisdiction claim matches the input. After iterating incoming 'id' edges, verifying each edge endpoint is an Organization, and comparing its jurisdiction claims (split into country/region parts), no candidate matched, so this error is returned.

Source

Thrown at engine/plugins/support/org/claims.go:281

						continue
					}
					jv := jc.PropertyValue

					if strings.EqualFold(jurisdiction, jv) {
						return orgent, nil
					} else if country != "" && strings.EqualFold(country, jv) {
						return orgent, nil
					} else if parts := strings.Split(jv, "-"); len(parts) == 2 && strings.EqualFold(jurisdiction, parts[0]) {
						return orgent, nil
					} else if len(parts) == 2 && strings.EqualFold(country, parts[0]) {
						return orgent, nil
					}
				}
			}
		}
	}

	return nil, fmt.Errorf("failed to obtain the Organization associated with jurisdiction %s and registration ID %s", jurisdiction, regID)
}

View on GitHub (pinned to 79299dce87)

Solutions

Confirm the jurisdiction string format (alpha-2 country and optional region) matches how claims were stored; align with countries.ByName normalization used by CreateOrgAsset.
Create the missing jurisdiction claim on the resolved Organization via CreateOrgJurisdictionClaim.
Inspect the graph to ensure the identifier's incoming edges point to the correct Organization asset.
Accept the miss: CreateOrgAsset falls back to norm-name+jurisdiction lookup or creates a new asset.

Defensive patterns

Strategy: fallback

Try / catch

if _, err := org.FindOrgByJurisdictionAndRegistrationIDClaim(sess, jurisdiction, regID); err != nil {
    // create the missing jurisdiction claim on the resolved org or create a new asset
    org.CreateOrgJurisdictionClaim(sess, orgent, jurisdiction)
}

Prevention

Use consistent jurisdiction formats (alpha-2, optional region) everywhere.
Create jurisdiction claims when registering the ID so lookups match.
Verify identifier edges point to the correct Organization after dedup.
Handle multi-jurisdiction registration IDs by scoping claims per jurisdiction.

When it happens

Trigger: The registration_id Identifier exists with incoming edges, but each edge's target Organization either fails verification, lacks a jurisdiction claim, or its jurisdiction/country doesn't match the requested jurisdiction string (e.g., input 'US-DE' vs stored 'US').

Common situations: Registration ID recorded under a different jurisdiction than queried; jurisdiction claims never created for the resolved org; region-qualified jurisdictions ('US-DE') vs plain country codes ('US') mismatching; duplicated registration IDs across jurisdictions.

Understand the failure class

Background: "Not found" and "does not exist" errors: why "Task not found", "No such folder", and "Can't find" fire when a lookup comes back empty — this error's family across 14 libraries.

Related errors

AI-assisted analysis of owasp-amass/amass@79299dce87 (2026-09-06). Data as JSON: /api/errors/7b38c5bf68b68e65. Report an issue: GitHub.