On 24/01/2019, Marc Roos wrote:
>
>
> This should do it sort of.
>
> {
> "Id": "Policy1548367105316",
> "Version": "2012-10-17",
> "Statement": [
> {
> "Sid": "Stmt1548367099807",
> "Effect": "Allow",
> "Action": "s3:ListBucket",
> "Principal": { "AWS": "arn:aws:ia
Ha Son Hai wrote:
> Hello everyone,
> I try to apply the bucket policy to my bucket for LDAP user but it doesn't
> work.
> For user created by radosgw-admin, the policy works fine.
>
> {
>
> "Version": "2012-10-17",
>
> "Statement": [{
>
> "Effect": "Allow",
>
> "Principal": {"AWS": [
Good day,
I've just merged some changs into master that set us up to compile
with C++17. This will require a reasonably new compiler to build
master.
Due to a change in how 'noexcept' is handled (it is now part of the type
signature of a function), mangled symbol names of noexcept functions are
d
On 07/11/2017, Simon Leinen wrote:
> Simon Leinen writes:
> > Adam C Emerson writes:
> >> On 03/11/2017, Simon Leinen wrote:
> >> [snip]
> >>> Is this supported by the Luminous version of RadosGW?
>
> >> Yes! There's a few bugfixes in
On 06/11/2017, nigel davies wrote:
> ok i am using Jewel vershion
>
> when i try setting permissions using s3cmd or an php script using s3client
>
> i get the error
>
> encoding="UTF-8"?>InvalidArgumenttest_bucket
> (truncated...)
>InvalidArgument (client): - encoding="UTF-8"?>InvalidArgu
On 03/11/2017, Simon Leinen wrote:
[snip]
> Is this supported by the Luminous version of RadosGW?
Yes! There's a few bugfixes in master that are making their way into
Luminous, but Luminous has all the features at present.
> (Or even Jewel?)
No!
> Does this work with Keystone integration, i.e.
On 03/11/2017, nigel davies wrote:
> Hay all
>
> i am having some problems with S3 acls / policy
>
> I want to set up two buckets
> bucket_upload
> bucket_process
>
> and two users
> usr_upload
> usr_process
>
>
> I want to set up acl or policys where
>
> usr_upload can write to bucket_upload
>
> u
Graham Allan Wrote:
> I thought I'd try out the new bucket policy support in Luminous. My goal
> was simply to permit access on a bucket to another user.
[snip]
> Thanks for any ideas,
It's probably the 'blank' tenant. I'll make up a test case to exercise
this and come up with a patch for it. Sorr
On 31/07/2015, Mariusz Gronczewski wrote:
> Well, Centos 6 will be supported to 2020, and centos 7 was released a
> year ago so I'd imagine a lot of people haven't migrated yet and
> migration process is nontrivial if you already did some modificiations
> to c6 (read: fix broken as fuck init script
