Timeline for Sending Credentials On Each Request
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 23, 2018 at 15:06 | comment | added | Daniel Few | What I want to be able to do is read and write files to a windows network share from outside the domain - through a web application. The problem is - This would be 'easy' if I gave the IIS user full read and write access to every file on the network - and then through code handle permissions (however this would mean my web app is handling security which I don't want - I want to use the already existing windows permissions - so ideally I need to do things like 'list contents of directory' server-side AS the user that has authenticated. I really hope that makes sense! | |
| Jan 22, 2018 at 22:32 | comment | added | McMatty | If you are using a framework then you are limited to what it allows. Is this on the same network - could use use windows auth and just rely on it sending the NTLM hash? | |
| Jan 22, 2018 at 20:57 | comment | added | Daniel Few | Link to SMB api to hopefully add context: github.com/icewind1991/SMB - with each request I have to reconnect with $server = new Server('localhost', 'username', 'password'); - unless there's a way I can make that connection once and store it for future use with the users credentials. | |
| Jan 22, 2018 at 20:56 | comment | added | Daniel Few | Thank you for the comment - The problem I have is with each call to my api - it has to re-authenticate with smb - to make a connection to the file server and get the new file/directory list - Does this mean I have to store their LDAP credentials server-side while they are logged in? - I hope I am making sense. | |
| Jan 22, 2018 at 20:46 | history | answered | McMatty | CC BY-SA 3.0 |