Planned for 11.32 Validation of fields in SSL CSR tool [Case 57237]

[jpratt]

I recommend the following improvements for the error messages when validating input for the SSL Certificate Signing Request (CSR) tool:

1) If the Country is left blank, the error "Field can contain only alpha characters" doesn't need to show. Currently both error messages show at once, causing this one to overlap the next field's box.
2) Why not validate the password field before the "generate" button is clicked, requiring 5 characters up front.

[jpratt]

3) and validate State, requiring 2 characters up front...etc

[jpratt]

Also, In Internet Explorer, the text displacement overlapping the box below is especially exaggerated. Also needed on the CRT screen

[jpratt]

And why not have the CRT tool have the ability to rename previous CRT files for the same domain name to end with .old, similar to the Key tool? So if the same domain has another CRT uploaded, there is still a link to the old CRT?

[jpratt]

The IE incompatibility seems related to this Case# involving email password text (very similar, FYI): ID # 51660

[cPanelDavidG]

The IE incompatibility seems related to this Case# involving email password text (very similar, FYI): ID # 51660

Update: Case 51660 has been resolved in versions 11.31.3.2 and later

[Cannet]

A drop down selection for country would be nice to ensure the correct country code is used.
As a UK based SSL reseller, most customer issues are from cPanel users with incorrect country codes.

[cPanelDavidG]

A drop down selection for country would be nice to ensure the correct country code is used.
As a UK based SSL reseller, most customer issues are from cPanel users with incorrect country codes.

Can you elaborate? Is this a matter of people entering BR or GB instead of UK, or is this about something else?

[monarobase]

+1 for either a drop down or at least an automatic check that the country code is in the list of allowed codes.

A dropdown would need to have the country names and for them to all be translated where as a check that the code is valid on form submission would probably be easier and from our point of view just as efficient.

For someone from england, I'm not sure that it's obvious that it's UK and not GB but if the system says that GB is not a valid code I think that most people would try UK next.

[monarobase]

3) and validate State, requiring 2 characters up front...etc

The state is not an easy one. Lots of countries don't have states. We tend to put our country code in a second time for this one although I'm not sure what the best practice is. If country is US than you should defenetly validate state, if it is not then you shoud, if it is best practice, allow no input and replace it automaticaly with the country code or what ever is supposed be put there when state is not applicable.

[Cannet]

Can you elaborate? Is this a matter of people entering BR or GB instead of UK, or is this about something else?

For someone from england, I'm not sure that it's obvious that it's UK and not GB but if the system says that GB is not a valid code I think that most people would try UK next.

Not wanting to be smart assed, but your comments kinda make the point perfectly, since it is in fact GB that is the accepted format, whereas most people from the UK, use UK, which returns an "Invalid country code" in any CSR parser.

[cPanelDavidG]

Not wanting to be smart assed, but your comments kinda make the point perfectly, since it is in fact GB that is the accepted format, whereas most people from the UK, use UK, which returns an "Invalid country code" in any CSR parser.

Is there a published list on what CSRs will accept? Given UK is the country code for people in that geographic region according to many standards, to block UK and allow GB presents an oddity that may indicate other deviations from international standards we need to accommodate.

[monarobase]

From what I have found doing a search on this :

Seems that it is the ISO 3166-1 2 letter country codes :

ISO - Maintenance Agency for ISO 3166 country codes - Country names and code elements
ISO 3166-1 - Wikipedia, the free encyclopedia

And from Verisign :

https://certmanager.verisign.com/mce...untrycodes.htm

[cPanelDavidG]

From what I have found doing a search on this :

Seems that it is the ISO 3166-1 2 letter country codes :

ISO - Maintenance Agency for ISO 3166 country codes - Country names and code elements
ISO 3166-1 - Wikipedia, the free encyclopedia

And from Verisign :

https://certmanager.verisign.com/mce...untrycodes.htm

I thank you very much, this is very useful information.

[cPanelDavidG]

Update: I've submitted this request to our developers since it was fairly straightforward: the country field should always be validated against the list of country codes in ISO 3166-1.

Thanks!