Checklist
Describe the problem you'd like to have solved
Hi team,
We're migrating from go-auth0 v1 to v2 and encountering significant breaking changes in connection management and types.
Example: v1's management.ConnectionOptionsSAMLIdpInitiated doesn't exist in v2. It only appears as part of management.SelfServiceProfileSSOTicketIdpInitiatedOptions, which seems intended for the new SelfService SSO setup flow. All of the SAML connection management types have not been carried over to v2
Describe the ideal solution
Questions:
- Are you planning to add the old types to v2?
- Should we use custom maps instead of typed structs?
- Is the intended approach to use the self-service ticket flow rather than direct connection management?
Ideally I would expect all the old types to still exist in the new package as well maybe under different names etc. since the auth0 api supports creating and managing connections.
Alternatives and current workarounds
Current workarounds are using custom maps.
Additional context
No response
Checklist
Describe the problem you'd like to have solved
Hi team,
We're migrating from go-auth0 v1 to v2 and encountering significant breaking changes in connection management and types.
Example: v1's
management.ConnectionOptionsSAMLIdpInitiateddoesn't exist in v2. It only appears as part ofmanagement.SelfServiceProfileSSOTicketIdpInitiatedOptions, which seems intended for the new SelfService SSO setup flow. All of the SAML connection management types have not been carried over to v2Describe the ideal solution
Questions:
Ideally I would expect all the old types to still exist in the new package as well maybe under different names etc. since the auth0 api supports creating and managing connections.
Alternatives and current workarounds
Current workarounds are using custom maps.
Additional context
No response