Timeline for Foreign Data Wrappers & Windows Authentication
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Apr 13, 2017 at 12:42 | history | edited | CommunityBot |
replaced http://dba.stackexchange.com/ with https://dba.stackexchange.com/
|
|
| Apr 5, 2015 at 21:45 | vote | accept | Nelson | ||
| Apr 2, 2015 at 16:53 | answer | added | Nelson | timeline score: 1 | |
| Apr 2, 2015 at 15:06 | comment | added | Craig Ringer | It'd be quite tricky to support this I think. We'd probably have to have a way to tunnel the credentials request from the Windows server through the FDW and to the client, or we'd need some kind of proxy/delegation rights given to the PostgreSQL server so it can "act as" any user. | |
| Apr 2, 2015 at 13:06 | comment | added | Nelson | Yeah I'll think the same but switching authentication its not really my call, I thought there might be a way around this... | |
| Apr 2, 2015 at 13:04 | comment | added | user1822 | As far as I know you can never use Windows authentication if the client is not a Windows host either. For example: Microsoft only ships Windows DLLs for their JDBC driver to enable Windows authentication. Your Postgres server is the client (from SQL Server's point of view) and is connecting from a non-Windows OS. I think you will have a lot less headaches if you switch SQL Server to mixed authentication and use a SQL Server user for the FDW. | |
| Apr 2, 2015 at 13:00 | history | asked | Nelson | CC BY-SA 3.0 |