Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CustomDomainVerificationResponse is missing a property for the cname_api_key #757

Open
5 tasks done
tmschlot opened this issue Dec 13, 2024 · 0 comments
Open
5 tasks done
Labels
bug This points to a verified bug in the code

Comments

@tmschlot
Copy link

Checklist

  • I have looked into the Readme and have not found a suitable solution or answer.
  • I have looked into the API documentation and have not found a suitable solution or answer.
  • I have searched the issues and have not found a suitable solution or answer.
  • I have searched the Auth0 Community forums and have not found a suitable solution or answer.
  • I agree to the terms within the Auth0 Code of Conduct.

Description

When attempting to verify a custom domain with self-managed certificates using the Management API, the SDK fails to return the cname_api_key value. You can only get this value at the time of verification, so it should be included in the CustomDomainVerificationResponse.

I propose adding a CnameApiKey -- or similarly-named -- property to that response that maps to the cname_api_key in the HTTP response.

Management API documentation Verify a custom domain Response Schema

Reproduction

  1. Create a custom domain using self_managed_certs.
  2. Create the DNS verification record.
  3. Verify the custom domain using the SDK, and there is no way to get the cname_api_key.

Additional context

No response

auth0.net version

7.30.0

.NET version

8

@tmschlot tmschlot added the bug This points to a verified bug in the code label Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This points to a verified bug in the code
Projects
None yet
Development

No branches or pull requests

1 participant