User Access Management - Design and POC

[Tejas-ChandraShekarRaju]

Overview.

Currently the storage service does not have a user hierarchy. Which means all functionalities that can be used are assumed to be a for single user.

Expectation

• [ ] As a contributor, I need to design and implement a user hierarchy feature within the system. This hierarchy will begin with a simple structure resembling folders, allowing for additional levels of organization. Currently, uploaded values are stored in a format such in a single bin file(bucket). The objective is to transition to a structure where a user can have multiple buckets and different users have their own namespace within the system.
• [ ] Authentication and Authorization - Support for different auth flows
• [ ] Identity management - Should we have the option to create user and manage users or should we use providers like google

[Tejas-ChandraShekarRaju]

@suryamurugan @Neerajgowda2611 We can continue our discussion here.

CC : @noobed-max

[suryamurugan]

@noobed-max checkout https://github.com/casdoor/casdoor-rust-sdk

[Tejas-ChandraShekarRaju]

@Neerajgowda2611 Check out Casdoor and understand what it means for applications to use them. And draw up a simple application life cycle with Casdoor as the UAM and we'll start from there.

Any application related queries specific to Storage service @noobed-max will help.

Once the we have a good understanding we'll look into code.

[Tejas-ChandraShekarRaju]

@Neerajgowda2611 add any updated documentation and thoughts here.