Jira (PUP-2551) Certname must be lowercase error not helpful

[Chad Metcalf (JIRA)]

Chad Metcalf created an issue

Puppet / PUP-2551 Certname must be lowercase error not helpful Issue Type: Bug Assignee: Unassigned Created: 12/May/14 10:19 PM Priority: Normal Reporter: Chad Metcalf Currently if you set a non lowercase certname you get this error: Error: Could not initialize global default settings: Certificate names must be lower case; see #1168 Its not terribly helpful for a couple reasons. We've moved away from RedMine. Only seasoned puppet veterans will see #1168 and say "oh right, redmine, duh." #1168 is an ancient thread that represents a dark time in puppet's history we'd all rather forget. Who cares about these comments? We need a succinct snippet for why we require lowercase names. Not force new users to read the insane old days. Especially since there really isn't any resolution on that thread. I seem to recall there was a better resource somewhere that had a more definitive explanation. I've helped numerous people get past this. Add Comment

This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)

[Eric Sorenson (JIRA)]

Eric Sorenson commented on an issue

Re: Certname must be lowercase error not helpful I am not going to re-open the original problem for further debate, but I agree it's completely terrible. Christopher Price can you make sure this is not the case (hah-hah no pun intended) in the new CA service? i.e. we should permit mixed-case (and indeed mixed character) subject names and not store the files on disk in a character-for-character representation of the certificate's subject name because this + https://projects.puppetlabs.com/issues/15561 We can remove the agent warning/restriction once we're no longer on the Ruby CA.

Add Comment

Puppet / PUP-2551 Certname must be lowercase error not helpful

Currently if you set a non lowercase certname you get this error:

{code}

Error: Could not initialize global default settings: Certificate names must be lower case; see #1168

{code}

Its not terribly helpful for a couple reasons.

# We've moved away from RedMine. Only seasoned puppet veterans will see #1168 and say "oh right, redmine, duh." # #1168 i...

[Zachary Stern (JIRA)]

Zachary Stern commented on an issue

Re: Certname must be lowercase error not helpful

Would it be possible in the interim to simply provide a better error message, without doing any actual fixing of the problem in the current CA?

Add Comment

[Eric Sorenson (JIRA)]

Eric Sorenson commented on an issue

Re: Certname must be lowercase error not helpful

Zachary Stern sure that's reasonable, can you work up a patch?

Add Comment

[Zachary Stern (JIRA)]

Zachary Stern commented on an issue

Re: Certname must be lowercase error not helpful

Eric Sorenson I can, but having read the redmine ticket top to bottom several times, I'm not quite sure what it should say. I get that the CA, currently, doesn't support mixed-case certnames, but I'm not quite sure what we'd want to give as the reason.

Add Comment

[Nick Walker (JIRA)]

Nick Walker commented on an issue

Re: Certname must be lowercase error not helpful

Do error messages really need to explain why something is not possible? Or only that you can't do whatever you tried to do?

Add Comment

[Zachary Stern (JIRA)]

Zachary Stern commented on an issue

Re: Certname must be lowercase error not helpful

I think in a case like this, where it's something you absolutely should be able to do (e.g. DNS names are not case sensitive, and on Windows machines, hostnames are by default upper case), then yes. In general, perhaps not.

Add Comment