PasswordChangeRequestTicket is missing Connection parameter
Dan3090 opened this issue · 1 comments
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
Description
The Auth0 documentation mentions the possibility of adding a connection_id for the Auth0 database when creating a password change ticket using the Auth0 Management API. However, despite providing all required information, a 400 Bad Request error is encountered, and the response indicates that the "connection is required."
Upon adding the field "connection": "",, the request succeeds with a 200 status. This issue persists when using the Auth0.ManagementApi library.
Expected Behavior
The expectation is to include a Connection property on the PasswordChangeTicketRequest class.
Reproduction Steps
No specific reproduction steps mentioned.
Environment
Version of this library used: 7.25.1
Framework: .NET 6.0
Additional Information
No other relevant modules, plugins, or libraries are involved.
Reproduction
Follow the steps on https://auth0.com/docs/authenticate/database-connections/password-change
Additional context
No response
auth0.net version
7.25.1
.NET version
6.0
In order to change the password using our SDK, you can:
- Call ChangePasswordAsync:
- This takes a parameter of type ChangePasswordRequest
- Which extends UserMaintenanceRequestBase and contains Connection.
This would allow you to do exactly what is explained in https://auth0.com/docs/authenticate/database-connections/password-change.
The expectation is to include a Connection property on the PasswordChangeTicketRequest class.
PasswordChangeTicketRequest is not used for achieving the same thing as explained in the link you shared.
Instead, it is used to call the tickets/password-change endpoint. This has no connection property, but only connection_id, which we support.
Closing, as it looks like everything works as expected. Can always reopen if needed.