Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Functionality to map home directory to different storage providers #1142

Merged
merged 4 commits into from
Sep 18, 2020

Conversation

ishank011
Copy link
Contributor

@ishank011 ishank011 commented Sep 4, 2020

We hardcode the home path for all users to /home. This forbids redirecting requests for different users to multiple storage providers. This PR provides the option to map the home directories of different users using user attributes.

For example, with home_mapping set to /user/{{substr 0 1 .Username}}, /home/abc for einstein could now be redirected to the storage provider corresponding to the rule /user/e and for marie, it could be redirected to that referred by the rule /user/m.

Also closes #1145

@ishank011 ishank011 requested a review from labkode as a code owner September 4, 2020 15:36
@ishank011 ishank011 requested a review from diocas September 4, 2020 15:36
SamuAlfageme added a commit to SamuAlfageme/cs3orgcharts that referenced this pull request Sep 17, 2020
This is specially useful when running into sharded scenarios as
e.g. different storage providers to map users with different
rules. Ref. cs3org/reva#1142

This commit contains a preliminary version, where the "real"
uniqueness of each replica in the set (in terms of config) is yet
to be implemented. First version will simply rely on the hostname
as selector inside the 'configFiles' value for a user-provided
toml file.
@labkode labkode merged commit ecef02d into cs3org:master Sep 18, 2020
@ishank011 ishank011 deleted the home-sp-mapping branch September 18, 2020 10:20
SamuAlfageme added a commit to SamuAlfageme/cs3orgcharts that referenced this pull request May 11, 2021
This is specially useful when running into sharded scenarios as
e.g. different storage providers to map users with different
rules. Ref. cs3org/reva#1142

This commit contains a preliminary version, where the "real"
uniqueness of each replica in the set (in terms of config) is yet
to be implemented. First version will simply rely on the hostname
as selector inside the 'configFiles' value for a user-provided
toml file.
SamuAlfageme added a commit to SamuAlfageme/cs3orgcharts that referenced this pull request May 11, 2021
This is specially useful when running into sharded scenarios as
e.g. different storage providers to map users with different
rules. Ref. cs3org/reva#1142

This commit contains a preliminary version, where the "real"
uniqueness of each replica in the set (in terms of config) is yet
to be implemented. First version will simply rely on the hostname
as selector inside the 'configFiles' value for a user-provided
toml file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Hide 'client_secret' from basic auth on the revad logs
2 participants