#Configure Resolver Service

This guide shows you how to configure your Vidos resolver service to support different DID methods and customize its behavior. You'll learn to enable and disable DID methods, test configuration changes, and optimize your resolver for your specific use cases.

#Prerequisites

Before configuring your resolver service, ensure you have:

• A Vidos account with access to the dashboard
• Basic understanding of DID resolution concepts
• Understanding of supported DID methods

#What you'll accomplish

By following this guide, you'll be able to:

• View and modify DID method configurations
• Enable and disable specific DID methods
• Test configuration changes in real-time

#Step 1: Access resolver configuration

Navigate to your resolver configuration settings in the dashboard.

1. Navigate to Resolvers in your dashboard.

2. Click "View" next to your resolver instance.

3. Find the "Configuration" section on the instance details page.

4. Review the currently enabled DID methods.

The configuration shows which DID methods are currently enabled in your instance (such as key, web, jwk, ethr, cheqd, ion).

#Step 2: Modify DID method support

Learn how to enable and disable different DID methods based on your requirements.

#2.1 Disable a DID method

1. Locate the DID method you want to disable (e.g., key method).
2. Click the toggle or checkbox to disable it.
3. Save the configuration changes.
4. Test the change by trying to resolve a DID of that method type.

#2.2 Test disabled method

Verify your configuration changes work as expected. After disabling a DID method (e.g., key):

1. Go to the "Test" section on your resolver instance page.
2. Enter a DID of the disabled type: did:key:z82LkvjLm5cfkWTvkm3RwyWNKb5awAXKRFZUDGjUhaXRAPE1Yx667dVszpiJTXMQsHRuZHN
3. Click "Test" to resolve the DID.
4. Verify you receive an error message about unsupported method.

#2.3 Enable a DID method

1. Locate the DID method you want to enable.
2. Click the toggle or checkbox to enable it.
3. Configure any additional settings required for that method.
4. Save the configuration changes.

#2.4 Test enabled method

After re-enabling the DID method:

1. Enable the key method in configuration.
2. Save the configuration changes.
3. Test the same DID again: did:key:z82LkvjLm5cfkWTvkm3RwyWNKb5awAXKRFZUDGjUhaXRAPE1Yx667dVszpiJTXMQsHRuZHN
4. Verify the DID now resolves successfully.

#Step 3: Configure response type

Learn how to modify the content type format of DID resolution responses to meet your application requirements.

#3.1 Test current response format

First, resolve a DID to see the current response format:

1. Go to the "Test" section on your resolver instance page.
2. Enter a DID to test: did:key:z82LkvjLm5cfkWTvkm3RwyWNKb5awAXKRFZUDGjUhaXRAPE1Yx667dVszpiJTXMQsHRuZHN
3. Click "Test" to resolve the DID.
4. Examine the response format - by default it uses application/did+ld+json format with JSON-LD context.

#3.2 Change to JSON format

Modify the response type to return standard JSON instead of JSON-LD:

1. Navigate to the "Configuration" section.
2. Locate the "Response Settings" or "Response Configuration".
3. Find the contentType setting (currently set to application/did+ld+json).
4. Change the content type to application/did+json.
5. Save the configuration changes.

#3.3 Test JSON format response

Verify the response format has changed:

1. Return to the "Test" section.
2. Test the same DID again: did:key:z82LkvjLm5cfkWTvkm3RwyWNKb5awAXKRFZUDGjUhaXRAPE1Yx667dVszpiJTXMQsHRuZHN
3. Compare the response - it should now be in standard JSON format without the @context field.
4. Verify the Content-Type header shows application/did+json.

#3.4 Restore default setting

Return to the default JSON-LD format:

1. Go back to the "Configuration" section.
2. Change the contentType setting back to application/did+ld+json.
3. Save the configuration changes.
4. Test the DID resolution again to confirm JSON-LD format is restored.

#Next steps

• Test Resolver Service - Testing your configured resolver
• Instance Configuration Best Practices - General configuration guidelines and best practices
• Instance State Management - Control and monitor instance operational status
• Instance Logs - Access and analyze instance logs

By following this configuration guide, you can customize your Vidos resolver service to meet your specific requirements while maintaining optimal performance and reliability.