Twitter Consumer Key not accepted


(Nitai ) #1

Hi there,

Setup a new server. However creating a new Twitter application for sign in and copying the Twitter Consumer Key results in an error message in the Discourse Admin with " Value doesn’t match the required format." The “twitter consumer secret” value is accepted however…

This is on the latest 0.9.9.18 version.


(Neil Lalonde) #2

Does it have a character other than letters, numbers, and underscores? We may need to remove or change our validation there. I think @riking added it.


(Kane York) #3

Now I’m betting it’s base64 and I failed to guess what their 64th character was.


(Nitai ) #4

Funny thing in an earlier Discourse version a key of
"14501908-N323uxz7wGn5bzIyalv3Dg2Jx2SDFSrGU36FQFsWS" was accepted, in
0.9.9.18 not anymore.

PS: This is not a valid key but with the same character length.


(Kane York) #5

This is the current regex we’re using to validate:

"^\\w*$"

Does your key have a character other than letters, numbers, and underscores? Please give us what character that is.


(Nitai ) #6

Just as posted in my previous reply.


(Kane York) #7

Oh! The dash. Okay then. I’ll submit a fix…


(Nitai ) #8

That’s great. Thank you.