I am using cert authentication to authenticate. I have created a user with name S114546 (with uppercase 'S'). user created is s114546 (with lowercase 's').
isn't it strange behavior? while creating the user it ignores the case but checks the case during authentication.
It is what it is...that you can write transient SQL with case-folding behavior doesn't mean other contexts (in this case the O/S) are going to behave the same way. Regardless, it is case-sensitive through-and-through which is not strange.
I can create the user with uppercase 'S' by double quoting the username. but the script which creates the user will do the same for all users which i do not want.
It seems considerably easier to modify your database role creation compared to the PKI certification creation. I suggest you figure out what you can live with on that front.
