| From: | Lindsay Stevens <lindsay(dot)stevens(dot)au(at)gmail(dot)com> |
|---|---|
| To: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: NTLM |
| Date: | 2016-12-06 21:36:40 |
| Message-ID: | CAG2CW_JXzV2fM+zwDi+F6pxcwWoYiQU_hjd-PofqdA736hbTQA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
It's an option for processing the user name of an authenticated user. It's
used to control whether you get "myuser" or "mydomain\myuser" as the user
name for mapping to a postgres login role.
So it doesn't impact SSPI directly, although they're related processes.
Consider pg_hba to be the bouncer, you have to get past their requirements
before the club owner (postgres) checks if you're on the guest list (login
roles) and lets you in. In this example include realm is like checking
either your name (0), or name and home town (1) against the guest list.
On 7 Dec 2016 1:59 am, "Branden Huggins" <branden.huggins@
rockwellcollins.com> wrote:
> In what situation will NTLM consider the include_realm=1 option of sspi?
>
> --
> Branden Huggins
> Software Engineering Co-op
> Rockwell Collins Simulation & Training Solutions
> 22640 Davis Drive
> Sterling, VA 20164
> (703) 885-8513
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Korot | 2016-12-07 04:48:36 | Connection failed [was: Re: Distribution package for OSX] |
| Previous Message | Branden Huggins | 2016-12-06 14:58:49 | NTLM |