Auth/EPP Keys Too long

[whitetiger264]

When requesting an Auth Code/EPP Key for transfer, I am presented with the following text dec8da9c7bd40e3cae51d7b2bf930ea3e19db55045304160a9aae69cf5fa11f7353526153691e47fc39868d705c32466a6b4569642bbd6b6bbxxxxxxxxxxxxxxxxxxx This is way too long. Can you look at shortening it?

[getpinga]

This is something with your registry, as currently we generate much shorter. Did you find a fix? Or let me know what is the registry you connect to. Thank you.

[whitetiger264]

I am using another WHMCS module, and the EPP keys we get are short, I do not think it is the registry in this case. The registry we're using uses the CoCCA system.

[getpinga]

I'll try to get Cocca instance to test, I think they don't use anymore the authcode like before, they generate the password on request. And maybe it is done in the module which itself sets temporarily the password. What my module pulls from EPP is some hash which is useless.

[getpinga]

Can you please tell me which module you are using? It seems for Cocca must be done domain update with new random auth code and then show this code.

[whitetiger264]

A WHMCS module that Cocca released or provided a few years back. I am not sure if I can share it, as I have no idea what legal implications it may have.

[getpinga]

I know about it, but it seems to have disappeared from the Internet. So don't share it, the one I found from them is what I mentioned - generating random authcode, updating the domain and then displaying it. Will see how to integrate it.

[whitetiger264]

Yep, should be that one. It seems it's just MIA, which is why I am hesitant to send it. It does, however, seem that @dnsguru was the last to work on it in 2020. Maybe we can get a comment on this.

[dnsguru]

Yep, should be that one. It seems it's just MIA, which is why I am hesitant to send it. It does, however, seem that @dnsguru was the last to work on it in 2020. Maybe we can get a comment on this.

I did a quick refresh of the documentation on the whmcs module back in 2020 to catch it up.

Now that I look, it appears CoCCA are not listing it so it may be something they include upon request. Not much help, but there is your comment

[dnsguru]

They operate on wafer-thin income and depend on their licensing to help drive development and support.

I would recommend contacting CoCCA directly with the contact you work with to license and consider using the most recent patch.

[whitetiger264]

Thank you @dnsguru the feedback is appreciated.

[getpinga]

Thank you, both. I found the needed explanation https://cocca.org.nz/srs/faq.html