RE: Newbee: Understanding question WebDAV-Protocoll
Hello mate, If you need to do change the lastModified time of a resource, I would consider that an hacker wish ;) No way you're going to be able to that, especially if you are using the client API. You would need to change server behavior, and in a way that the server would not follow webdav specification directives. The reason is pretty straightforward: webdav specification states that resources have live and dead properties, being the dead properties the ones we can PROPPATCH, that is, we can create, update and remove them from the resource. The live properties values, like lastModified, creationDate, contentLength, contentType, are calculated in real time (maybe stored afterwards) with server information. For that reason, they are protected, and can't be changed by the user (I'll just copy paste and excerpt from rfc4918): Live Property - A property whose semantics and syntax are enforced by the server. For example, the live property DAV:getcontentlength has its value, the length of the entity returned by a GET request, automatically calculated by the server. I believe that the protected method setGetLastModified purpose is to set the date value on the local image of a remote resource. So overriding won't help you on your intention. I don't know why you must change lastModified value, but if it is a business decision, I would suggest you to create a new property for storing the value that you want (ex: insert your namespace here:getLastModified). Hope this helps, Miguel Figueiredo -Original Message- From: pk_jsp [mailto:[EMAIL PROTECTED] Sent: quinta-feira, 13 de Setembro de 2007 22:16 To: slide-user@jakarta.apache.org Subject: RE: Newbee: Understanding question WebDAV-Protocoll Hi Miguel, I was wandering into this list and read this thread in whole. A very brief introduction: I am using Webdav to programatically (Java) bulk import text files from local drive into EMC eRoom Server. This line explains all my environment. I am using Slide client library. Can you help me in this specific question: By default the lastModified time of imported file is the current time when it is imported. Can I override this behaviour and retain the original time from source location. The 'WebdavFile' class has no such method. But 'WebdavResource' has a method setGetLastModified but it is protected. I think if I extend it in my custom class I can achieve this. Any comments on this. -- View this message in context: http://www.nabble.com/Newbee%3A-Understanding-question-WebDAV-Protocoll-tf41 02995.html#a12663741 Sent from the Jakarta Slide - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Authentication with Slide - Slide vs tomcat Realm
Hi Satish, look for JAAS-Authentication that is a standard API that works pretty well with tomcat. A good introduction is found at http://www.javaworld.com/javaworld/jw-09-2002/jw-0913-jaas.html Yours Arne Satish schrieb: Hi I need to authentication with Slide, there are two ways I can see I am thinking of using Slide realm and configuring tomcat to use Slide user database for authentication. Otherwise if I rely completely on tomcat realm, typical tomcat-users.xml file based, authetication, I need to add user two places - Slide and tomcat-user, which is problem. Can any body suggests on #1 how can I configure tomcat to use the Slide users for authentication? #2 how can I actually autheticate request of tomcat programatically, is any API available? What I am looking for is authenticating user with Slide. Any suggestion is valuable for me. Regards, Satish Disclaimer: This e-mail may contain Privileged/Confidential information and is intended only for the individual(s) named. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. Please notify the sender, if you have received this e-mail by mistake and delete it from your system. Information in this message that does not relate to the official business of the company shall be understood as neither given nor endorsed by it. E-mail transmission cannot be guaranteed to be secure or error-free. The sender does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Visit us at http://www.harbinger-systems.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Authentication with Slide - Slide vs tomcat Realm
Hi I need to authentication with Slide, there are two ways I can see I am thinking of using Slide realm and configuring tomcat to use Slide user database for authentication. Otherwise if I rely completely on tomcat realm, typical tomcat-users.xml file based, authetication, I need to add user two places - Slide and tomcat-user, which is problem. Can any body suggests on #1 how can I configure tomcat to use the Slide users for authentication? #2 how can I actually autheticate request of tomcat programatically, is any API available? What I am looking for is authenticating user with Slide. Any suggestion is valuable for me. Regards, Satish Disclaimer: This e-mail may contain Privileged/Confidential information and is intended only for the individual(s) named. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. Please notify the sender, if you have received this e-mail by mistake and delete it from your system. Information in this message that does not relate to the official business of the company shall be understood as neither given nor endorsed by it. E-mail transmission cannot be guaranteed to be secure or error-free. The sender does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Visit us at http://www.harbinger-systems.com/
Re: Authentication with Slide - Slide vs tomcat Realm
Hey Arne Thanks for quick reponse. Do you mean here that I should take steps below to implemnt authetication, - configure Slide realm, configure tomcat to use Slide users for authentication - configure JAAS for tomcat - use JAAS API to authenticate the requests, so here JAAS will ask tomcat for authetication - tomcat will check Slide user database Is is somthing gonna happen...? Thanks. Regards, Satish - Original Message - From: Arne v.Irmer [EMAIL PROTECTED] To: Slide Users Mailing List slide-user@jakarta.apache.org Sent: Friday, September 14, 2007 2:50 PM Subject: Re: Authentication with Slide - Slide vs tomcat Realm Hi Satish, look for JAAS-Authentication that is a standard API that works pretty well with tomcat. A good introduction is found at http://www.javaworld.com/javaworld/jw-09-2002/jw-0913-jaas.html Yours Arne Satish schrieb: Hi I need to authentication with Slide, there are two ways I can see I am thinking of using Slide realm and configuring tomcat to use Slide user database for authentication. Otherwise if I rely completely on tomcat realm, typical tomcat-users.xml file based, authetication, I need to add user two places - Slide and tomcat-user, which is problem. Can any body suggests on #1 how can I configure tomcat to use the Slide users for authentication? #2 how can I actually autheticate request of tomcat programatically, is any API available? What I am looking for is authenticating user with Slide. Any suggestion is valuable for me. Regards, Satish Disclaimer: This e-mail may contain Privileged/Confidential information and is intended only for the individual(s) named. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. Please notify the sender, if you have received this e-mail by mistake and delete it from your system. Information in this message that does not relate to the official business of the company shall be understood as neither given nor endorsed by it. E-mail transmission cannot be guaranteed to be secure or error-free. The sender does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Visit us at http://www.harbinger-systems.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Disclaimer: This e-mail may contain Privileged/Confidential information and is intended only for the individual(s) named. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. Please notify the sender, if you have received this e-mail by mistake and delete it from your system. Information in this message that does not relate to the official business of the company shall be understood as neither given nor endorsed by it. E-mail transmission cannot be guaranteed to be secure or error-free. The sender does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Visit us at http://www.harbinger-systems.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Authentication with Slide - Slide vs tomcat Realm
Hi Satish, things are easy, if you look at the used technics: Silde is a servlet in tomcat and uses the authentication mechanism of tomcat. This includes such nice things like the sso-Valve. What you have to implement a user management that does both: 1. Creating/Deleting the user in silde by just creating/deleting a collection with the user name in /user (default value). Tip: Look at the powerful roles mechanism in slide. 2. Doing the JAAS-Authentication. This is how we did it here. Yours Arne Satish schrieb: Hey Arne Thanks for quick reponse. Do you mean here that I should take steps below to implemnt authetication, - configure Slide realm, configure tomcat to use Slide users for authentication - configure JAAS for tomcat - use JAAS API to authenticate the requests, so here JAAS will ask tomcat for authetication - tomcat will check Slide user database Is is somthing gonna happen...? Thanks. Regards, Satish - Original Message - From: Arne v.Irmer [EMAIL PROTECTED] To: Slide Users Mailing List slide-user@jakarta.apache.org Sent: Friday, September 14, 2007 2:50 PM Subject: Re: Authentication with Slide - Slide vs tomcat Realm Hi Satish, look for JAAS-Authentication that is a standard API that works pretty well with tomcat. A good introduction is found at http://www.javaworld.com/javaworld/jw-09-2002/jw-0913-jaas.html Yours Arne Satish schrieb: Hi I need to authentication with Slide, there are two ways I can see I am thinking of using Slide realm and configuring tomcat to use Slide user database for authentication. Otherwise if I rely completely on tomcat realm, typical tomcat-users.xml file based, authetication, I need to add user two places - Slide and tomcat-user, which is problem. Can any body suggests on #1 how can I configure tomcat to use the Slide users for authentication? #2 how can I actually autheticate request of tomcat programatically, is any API available? What I am looking for is authenticating user with Slide. Any suggestion is valuable for me. Regards, Satish Disclaimer: This e-mail may contain Privileged/Confidential information and is intended only for the individual(s) named. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. Please notify the sender, if you have received this e-mail by mistake and delete it from your system. Information in this message that does not relate to the official business of the company shall be understood as neither given nor endorsed by it. E-mail transmission cannot be guaranteed to be secure or error-free. The sender does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Visit us at http://www.harbinger-systems.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Disclaimer: This e-mail may contain Privileged/Confidential information and is intended only for the individual(s) named. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. Please notify the sender, if you have received this e-mail by mistake and delete it from your system. Information in this message that does not relate to the official business of the company shall be understood as neither given nor endorsed by it. E-mail transmission cannot be guaranteed to be secure or error-free. The sender does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Visit us at http://www.harbinger-systems.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbee: Understanding question WebDAV-Protocoll
Miguel Figueiredo wrote: Hello mate, If you need to do change the lastModified time of a resource, I would consider that an hacker wish ;) No way you're going to be able to that, especially if you are using the client API. You would need to change server behavior, and in a way that the server would not follow webdav specification directives. The reason is pretty straightforward: webdav specification states that resources have live and dead properties, being the dead properties the ones we can PROPPATCH, that is, we can create, update and remove them from the resource. The live properties values, like lastModified, creationDate, contentLength, contentType, are calculated in real time (maybe stored afterwards) with server information. For that reason, they are protected, and can't be changed by the user (I'll just copy paste and excerpt from rfc4918): Live Property - A property whose semantics and syntax are enforced by the server. For example, the live property DAV:getcontentlength has its value, the length of the entity returned by a GET request, automatically calculated by the server. ... Well. This means that a server is *allowed* to reject a request setting DAV:getlastmodified. But it doesn't have to. Best regards, Julian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
