Ok, yes. It’s s server for analytics running R. So users speecify their oen connection string. My initial thought was to leave out username in the connection string, but I think now to
specify username in lowercase.
Thank you, and Magnus also.
Niels
Fra: Stephen Frost <[email protected]>
Dato: 30. august 2019 kl. 16.21.39 CEST
Til: Niels Jespersen <[email protected]>
Cc: Magnus Hagander <[email protected]>, [email protected] <[email protected]>
Emne: Re: SSPI auth and mixed case usernames
Greetings,
* Niels Jespersen ([email protected]) wrote:
> Hello Magnus
> Thank you for your prompt reply.
> I’m not sure I understand your last statement. I want to achieve that
> regardless of the case of the entered username is logged into the same
> Postgres user (whose name is created in all lowercase).
> In other words, Windows usernames one day entered as XYz, the next day
> entered as xYz, should logon to Postgres user xyz.
You just have to make sure that the users tell whatever program they're
using to connect to PG (like psql, pgAdmin, whatever) that their PG
username is 'xyz'. If they try to log in as 'XYZ' then that's gonna be
a different PG user.
If you have some other application that's being used to connect to PG
then you could do the lowercase in the app...
Thanks,
Stephen
* Niels Jespersen ([email protected]) wrote:
> Hello Magnus
> Thank you for your prompt reply.
> I’m not sure I understand your last statement. I want to achieve that
> regardless of the case of the entered username is logged into the same
> Postgres user (whose name is created in all lowercase).
> In other words, Windows usernames one day entered as XYz, the next day
> entered as xYz, should logon to Postgres user xyz.
You just have to make sure that the users tell whatever program they're
using to connect to PG (like psql, pgAdmin, whatever) that their PG
username is 'xyz'. If they try to log in as 'XYZ' then that's gonna be
a different PG user.
If you have some other application that's being used to connect to PG
then you could do the lowercase in the app...
Thanks,
Stephen
