The key file on this repo for this clean up is this utm-apis/fimsauthz-api/nup-roles.yaml which is used to generate the authorities_to_scope_mapping.json during the deployment process.
The key files in fims-authz repo (also FRED-800-update-nup-roles branch) are being cleaned up are below:
modules/fims-authz-sig/config/clients.json
modules/fims-authz-sig/config/authorities_to_scope_mapping.json
(For your quick reference, I attached both here)
The code that process and creates authorities_to_scope_mapping.json is fims-authz-sig/tools/generate_scopes_json/scope_me.js, which is called by fims-authz-sig/scripts/zip_for_deploy.sh during the deployment.
I want to get your review feedback earlier since you have the insights the legacy setup. Once the contents are correct, testing will be underway accordingly.
…ent env
The key file on this repo for this clean up is this utm-apis/fimsauthz-api/nup-roles.yaml which is used to generate the authorities_to_scope_mapping.json during the deployment process.
The key files in fims-authz repo (also FRED-800-update-nup-roles branch) are being cleaned up are below: modules/fims-authz-sig/config/clients.json modules/fims-authz-sig/config/authorities_to_scope_mapping.json (For your quick reference, I attached both here)
The code that process and creates authorities_to_scope_mapping.json is fims-authz-sig/tools/generate_scopes_json/scope_me.js, which is called by fims-authz-sig/scripts/zip_for_deploy.sh during the deployment.
I want to get your review feedback earlier since you have the insights the legacy setup. Once the contents are correct, testing will be underway accordingly.
clients.json.txt authorities_to_scope_mapping.json.txt