|

»

Problems using S3 Online Password Storage

View: New views

4 Messages — Rating Filter: Alert me

	Problems using S3 Online Password Storage by Michael Aram :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. Hi everybody, the Cockpit application generally works fine for me. Unfortunately the online password storage feature reports the following bug: invalid location constraint the other options (direct login, local storage) work fine. Is this a known issue? cheers
	Re: Problems using S3 Online Password Storage by James Murty-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hi Michael, This was not a known issue, thanks for letting me know. I have fixed the bug that caused this problem and have also updated the online version of Cockpit with the fix. If you are running Cockpit locally you can work around this issue in two ways: - Comment-out the property "s3service.default-bucket-location=US" in jets3t.properties. When this property is missing, all buckets will still be created in the US location. - Download the latest service jar file to replace the buggy version: https://jets3t.s3.amazonaws.com/applets-jets3t-0.6.0/jets3t-0.6.0.jar If you are building JetS3t from source, check out the latest version from CVS head to get the fix. Cheers, James On 2/10/08, Michael Aram <h9802641@...> wrote: Hi everybody, the Cockpit application generally works fine for me. Unfortunately the online password storage feature reports the following bug: invalid location constraint the other options (direct login, local storage) work fine. Is this a known issue? cheers
	Re: Problems using S3 Online Password Storage by Michael Aram :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Hi James! Thank you - it works now! I have a suggestion for an improvement: S3 unfortunately doesnt support folders. I dont like the "home grown" approaches, like JungelDisk or S3 Fox do. But: We could use a SubDomain-style bucket naming convention. What I mean is: Jets3t could provide a switch "display buckets in tree view", where a bucket named "letters.documents.example.com" is a subfolder of "documents.example.com" what do you think? This would perfectly fit into amazons S3-design, by still offering an intuitive way to create subfolders. cheers James Murty schrieb: Hi Michael, This was not a known issue, thanks for letting me know. I have fixed the bug that caused this problem and have also updated the online version of Cockpit with the fix. If you are running Cockpit locally you can work around this issue in two ways: - Comment-out the property "s3service.default-bucket-location=US" in jets3t.properties. When this property is missing, all buckets will still be created in the US location. - Download the latest service jar file to replace the buggy version: https://jets3t.s3.amazonaws.com/applets-jets3t-0.6.0/jets3t-0.6.0.jar If you are building JetS3t from source, check out the latest version from CVS head to get the fix. Cheers, James On 2/10/08, Michael Aram <h9802641@...> wrote: Hi everybody, the Cockpit application generally works fine for me. Unfortunately the online password storage feature reports the following bug: invalid location constraint the other options (direct login, local storage) work fine. Is this a known issue? cheers
	Re: Problems using S3 Online Password Storage by James Murty-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. Hi Michael, I don't think your idea to have folders based on sub-domain bucket names will work well. Because you can have no more than 100 buckets in S3, you would be limited to only 100 folders. In S3 you can create object key names using almost any character and the recommended way to create a pseudo-hierarchy is to use a delimiter character such as '/' in object names to denote a folder structure. In Cockpit, if you upload a directory structure the object keys will be created with names that represent the folders and files as a hierarchy. Cockpit displays all the objects in a single list rather than separating them out into folders as JungleDisk and S3 Fox do. I may one day provide an optional tree view for objects in Cockpit, but in the meantime the directories you upload with JetS3t and Cockpit will appear as a folder structure in S3 Fox. Cheers, James On 2/12/08, Michael Aram <h9802641@...> wrote: Hi James! Thank you - it works now! I have a suggestion for an improvement: S3 unfortunately doesnt support folders. I dont like the "home grown" approaches, like JungelDisk or S3 Fox do. But: We could use a SubDomain-style bucket naming convention. What I mean is: Jets3t could provide a switch "display buckets in tree view", where a bucket named "letters.documents.example.com" is a subfolder of "documents.example.com" what do you think? This would perfectly fit into amazons S3-design, by still offering an intuitive way to create subfolders. cheers James Murty schrieb: Hi Michael, This was not a known issue, thanks for letting me know. I have fixed the bug that caused this problem and have also updated the online version of Cockpit with the fix. If you are running Cockpit locally you can work around this issue in two ways: - Comment-out the property "s3service.default-bucket-location=US" in jets3t.properties. When this property is missing, all buckets will still be created in the US location. - Download the latest service jar file to replace the buggy version: https://jets3t.s3.amazonaws.com/applets-jets3t-0.6.0/jets3t-0.6.0.jar If you are building JetS3t from source, check out the latest version from CVS head to get the fix. Cheers, James On 2/10/08, Michael Aram <h9802641@...> wrote: Hi everybody, the Cockpit application generally works fine for me. Unfortunately the online password storage feature reports the following bug: invalid location constraint the other options (direct login, local storage) work fine. Is this a known issue? cheers