> Good solution, but this is a slightly different problem. The app server > authenticates the requests to my WebDAV GUI. I can find out the name, but > not the password. I need to send a request from my GUI to Slide, and I > want Slide to see it as coming from the same user. I need the Principal > from one request to be copied to the other request. Then Slide will create > a trusted CredentialsToken for that Principal, and use them for ACLs and > ownership stuff.
How does the application authenticate. If your using basic auth over http you can simply get the encoded auth header and send that in the header of the wedav request (this assumes that the application is trying to it's other communications via http). > I'm still scratching my head if anyone has any ideas. I can modify Slide > to accept some sort of cookie, but I was hoping to use it as-is. What value would you put into the cookie? k. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
