Currently, the contact is always included in the login process in Epp.php, even for registries that do not support contacts. To improve flexibility, consider making this configurable, similar to the handling of optional extensions in the config. This would allow disabling the contact for registries where it is not required or supported.
Recommendation:
- Move contact handling from hardcoded in
Epp.php login to a config option.
- Apply the same approach that is used for optional extensions.
- Ensure backward compatibility for registries that do require contacts.
Currently, the contact is always included in the login process in
Epp.php, even for registries that do not support contacts. To improve flexibility, consider making this configurable, similar to the handling of optional extensions in the config. This would allow disabling the contact for registries where it is not required or supported.Recommendation:
Epp.phplogin to a config option.