Running s3 service and creating users/policies via minio mc client for example with:
./mc admin user add nas-s3 user1
Will create a user that can be seen via "user list" and the relevant configs can be
seen with the s3 service directory:
[root@nas ~]# ls /mnt/tank/services/s3/.minio.sys/config/iam/
format.json groups policies policydb users
Creating groups and IAM resource policies all works fine. However, whilst these settings
persist after stopping the service, they appear to be removed when the s3 service is started again.
Upon restarting the service, everything in the "iam" dir except "format.json" has been removed
and users no longer have access to their buckets until recreated via "mc" cli again.
I've not used minio outside of TrueNAS, so I'm not sure if there's something I'm missing to
ensure IAM policies persist through restarts, or if this is a quirk/bug with how TrueNAS is using
it?
Anyone else run into this or have any suggestions for how to resolve it?
./mc admin user add nas-s3 user1
Will create a user that can be seen via "user list" and the relevant configs can be
seen with the s3 service directory:
[root@nas ~]# ls /mnt/tank/services/s3/.minio.sys/config/iam/
format.json groups policies policydb users
Creating groups and IAM resource policies all works fine. However, whilst these settings
persist after stopping the service, they appear to be removed when the s3 service is started again.
Upon restarting the service, everything in the "iam" dir except "format.json" has been removed
and users no longer have access to their buckets until recreated via "mc" cli again.
I've not used minio outside of TrueNAS, so I'm not sure if there's something I'm missing to
ensure IAM policies persist through restarts, or if this is a quirk/bug with how TrueNAS is using
it?
Anyone else run into this or have any suggestions for how to resolve it?