Skip to content

Commit 95773e3

Browse files
committed
W-21743430-goddady-fa
1 parent 6772f4e commit 95773e3

3 files changed

Lines changed: 144 additions & 72 deletions

File tree

modules/ROOT/pages/godaddy-overview.adoc

Lines changed: 23 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -1,64 +1,55 @@
11
= Register Agents with GoDaddy ANS
22

33
GoDaddy Agent Name Service (ANS) integration enables you to register and verify agents deployed through API Manager.
4-
Registration associates your agent with a verified domain and allows Anypoint Exchange to display a verified status for the asset.
4+
Registration associates your agent with a fully qualified domain name (FQDN) and establishes a verifiable identity based on domain ownership.
55

6-
This integration introduces a registration workflow in API Manager that communicates with GoDaddy to validate domain ownership and agent identity.
6+
This integration connects API Manager with GoDaddy to validate agent identity and surface verification status across the platform.
77

88
== Capabilities
99

1010
With GoDaddy ANS integration in API Manager, you can:
1111

1212
* Register an agent instance with GoDaddy ANS
13-
* Track the registration status directly from API Manager
14-
* Retry or restart registration if it fails or expires
15-
* Verify agents associated with your domain
13+
* Verify agent identity using domain ownership validation
14+
* Track verification progress directly from API Manager
1615
* Surface verification status in Anypoint Exchange
1716

18-
== Registration Workflow
17+
== Registration workflow
1918

20-
The registration workflow spans API Manager, GoDaddy, and Anypoint Exchange:
19+
The registration workflow spans API Manager, GoDaddy, and your DNS provider.
2120

22-
1. You initiate registration from an API instance in API Manager.
23-
2. API Manager sends a registration request to GoDaddy ANS.
24-
3. GoDaddy validates domain ownership using DNS or ACME challenges.
25-
4. API Manager tracks and updates the registration status.
26-
5. Once verification is complete, the agent is marked as verified.
27-
6. Anypoint Exchange displays the verified status for the asset.
21+
You initiate registration from an API instance in API Manager.
22+
GoDaddy then validates domain ownership using standard verification methods such as DNS or ACME challenges.
23+
API Manager tracks the progress of this process and updates the agent status once verification is complete.
2824

29-
The exact validation process depends on the domain type used by the agent.
25+
Depending on your domain configuration, some steps might require manual action.
3026

31-
== Supported Domain types
27+
== Consumer endpoint and FQDN
3228

33-
The registration experience varies depending on the domain associated with the agent:
29+
The consumer endpoint configured for the agent is used to derive a fully qualified domain name (FQDN) that uniquely identifies the agent.
3430

35-
* *MuleSoft-managed domains*:
36-
API Manager automatically handles DNS configuration and verification.
31+
This domain is registered as part of the verification process and represents the agent’s identity in GoDaddy ANS.
32+
After registration, the domain cannot be modified.
3733

38-
* *Custom domains*:
39-
You must manually configure DNS records to complete verification.
40-
If verification is not completed within the allowed time window, the registration expires and must be restarted.
34+
For more information, see https://www.godaddy.com/resources/skills/whats-a-fully-qualified-domain-name-fqdn-and-whats-it-good-for[What is a Fully Qualified Domain Name (FQDN)?].
4135

42-
== Registration status
36+
== Supported domain types
4337

44-
During registration, API Manager tracks the status of the verification process.
45-
Common states include:
38+
The registration experience varies depending on the domain associated with the agent:
4639

47-
* Pending validation
48-
* Waiting for DNS configuration
49-
* Active (verified)
50-
* Failed
51-
* Expired
40+
* *MuleSoft-managed domains*:
41+
API Manager handles domain configuration and verification automatically.
5242

53-
You can monitor the current status and take action, such as retrying the process, directly from API Manager.
43+
* *Custom domains*:
44+
You must configure DNS records in your DNS provider to complete verification.
45+
If verification is not completed within the allowed time window, the process must be restarted.
5446

5547
== Integration with Anypoint Exchange
5648

5749
Verification status is reflected in Anypoint Exchange:
5850

5951
* Verified agents display a visual indicator in search results and asset pages
6052
* Verification is tied to the agent instance and its associated domain
61-
* Only successfully verified agents are marked as verified
6253

6354
== Before you begin
6455

@@ -67,7 +58,7 @@ Before registering an agent, make sure that:
6758
* The API instance is deployed and accessible
6859
* A valid consumer endpoint is configured
6960
* Required credentials for GoDaddy ANS are available
70-
* You have permissions to manage the API instance and related secrets
61+
* You have access to manage DNS records for the domain, if using a custom domain
7162

7263
== See also
7364

Lines changed: 29 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -1,58 +1,47 @@
1-
= Register an agent
1+
= Create an agent instance
22

3-
Register an agent to verify its domain and enable its verified status in Anypoint Exchange.
4-
Registration is initiated from an API instance in API Manager and requires validating domain ownership through GoDaddy ANS.
3+
Create an agent instance in API Manager to expose your agent and configure its runtime, endpoint, and routing settings.
4+
5+
After creating the agent instance, you can verify its identity using GoDaddy ANS to associate it with a trusted domain and enable its verified status in Anypoint Exchange.
56

67
== Requirements
78

89
Before you begin, make sure that:
910

1011
* The API instance is deployed and accessible
11-
* A valid consumer endpoint is configured for the agent
12-
* You have access to the required GoDaddy ANS credentials
13-
* You have permissions to manage the API instance and related secrets
12+
* You have access to a target runtime (for example, Flex Gateway)
13+
* You have the required permissions to manage API instances
1414

15-
== Register an agent
15+
== Create an new agent instance
1616

1717
. In Anypoint Platform, go to *API Manager*.
18-
. Select the API instance that represents your agent.
19-
. In the instance details, locate the *Agent registration* section.
20-
. Click *Register agent*.
21-
. Provide the required configuration:
18+
. Click *Add new instance*.
19+
. Select the agent or API asset you want to deploy.
20+
. Configure the runtime settings:
2221
+
23-
* *Consumer endpoint*: The public endpoint used for verification
24-
* *Credentials*: The GoDaddy API key and secret required for registration. +
25-
Generate these credentials in your GoDaddy account and provide them during registration.
26-
. Click *Submit* to start the registration process.
27-
28-
API Manager initiates the registration request and displays the current registration status.
29-
30-
== Complete domain verification
31-
32-
Depending on the domain type, verification is completed differently:
33-
34-
* *MuleSoft-managed domains*:
35-
Verification is handled automatically. No additional action is required.
36-
37-
* *Custom domains*:
38-
You must create the required DNS records to complete verification.
39-
Use the values provided in API Manager to configure your DNS provider.
40-
41-
Verification must be completed within the allowed time window. If verification expires, you must restart the registration process.
42-
43-
== Monitor registration status
44-
45-
After submitting the registration:
22+
* Select the target gateway
23+
* Choose the deployment configuration
24+
+
25+
. Configure the endpoint settings:
26+
+
27+
* *Consumer endpoint*: The public endpoint where the agent will be exposed
28+
+
29+
This endpoint is used later for identity verification.
30+
+
31+
. Configure the upstream service:
32+
+
33+
* Provide the target service or backend configuration
34+
+
35+
. Review the configuration and click *Deploy*.
4636

47-
* View the current status in the *Agent registration* section
48-
* Wait for the status to transition to *Active* after successful verification
49-
* If the process fails or expires, use the available option to retry or restart registration
37+
After deployment, the agent instance is created and available in API Manager.
5038

5139
== Next steps
5240

53-
After the agent is successfully registered:
41+
After creating the agent instance:
5442

43+
* Verify the agent identity using GoDaddy ANS
44+
* Complete domain validation to enable verified status
5545
* Confirm that the agent displays as verified in Anypoint Exchange
56-
* Review the asset details and ensure the verified status is visible
5746

58-
For more information, see xref:placeholderside[Integration with Anypoint Exchange].
47+
For more information, see xref:placeholderside[Verify an agent using GoDaddy ANS].
Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
= Verify an agent using GoDaddy ANS
2+
3+
Verify an agent to establish a trusted identity based on domain ownership and enable its verified status in Anypoint Exchange.
4+
5+
Verification uses GoDaddy Agent Name Service (ANS) to validate the domain associated with the agent and confirm that you control it.
6+
7+
== Before you begin
8+
9+
Before verifying an agent, make sure that:
10+
11+
* The agent instance is created and deployed in API Manager
12+
* A valid consumer endpoint is configured for the agent
13+
* You have a GoDaddy account with API key and secret
14+
* You have access to manage DNS records for the domain
15+
* You have access to a secret group in Secrets Manager
16+
17+
== Start agent verification
18+
19+
. In Anypoint Platform, go to *API Manager*.
20+
. Select the API instance that represents your agent.
21+
. Click *Actions* > *Verify agent identity*.
22+
23+
The verification wizard opens and guides you through the required steps.
24+
25+
== Step 1: Provide prerequisites
26+
27+
In this step:
28+
29+
* Confirm or update the *Consumer endpoint*
30+
+
31+
The consumer endpoint is used to derive the domain that will be verified. This value becomes part of the agent’s identity and cannot be changed after registration.
32+
33+
* Select a *Secret group*
34+
+
35+
The secret group is used to store credentials and generated security artifacts required for verification.
36+
37+
NOTE: You must have access to at least one secret group to continue.
38+
39+
== Step 2: Enter GoDaddy ANS credentials
40+
41+
In this step, provide your GoDaddy credentials:
42+
43+
* *API key*
44+
* *API secret*
45+
46+
These credentials are used to communicate with GoDaddy ANS and initiate the verification process.
47+
48+
== Step 3: Verify domain ownership (ACME)
49+
50+
To prove domain ownership, you must create a DNS TXT record.
51+
52+
. Copy the provided record details.
53+
. In your DNS provider, create the TXT record.
54+
. Return to API Manager and click *Verify*.
55+
56+
API Manager checks whether the record has been propagated and validated.
57+
58+
== Step 4: Verify DNS records
59+
60+
After ACME verification, additional DNS records are generated.
61+
62+
. Copy the provided DNS records.
63+
. Add them to your DNS provider.
64+
. Click *Verify*.
65+
66+
These records enable secure communication and complete the identity verification process.
67+
68+
== Verification process
69+
70+
Verification is asynchronous and depends on DNS propagation and external validation.
71+
72+
* Status updates are displayed in API Manager
73+
* Verification can take several minutes or longer depending on DNS updates
74+
* API Manager continuously checks the status after verification is initiated
75+
76+
You can close the verification dialog and return later. The status continues to update in the background.
77+
78+
== Retry or restart verification
79+
80+
If verification is not completed:
81+
82+
* DNS records may expire after a limited time
83+
* You can restart the verification process from the agent instance
84+
* New DNS records are generated when restarting
85+
86+
== After verification
87+
88+
When verification is successful:
89+
90+
* The agent is marked as verified in API Manager
91+
* A verified indicator appears in Anypoint Exchange
92+
* The agent is associated with a trusted domain identity

0 commit comments

Comments
 (0)