Tenant-conf changes for customizing auth header per tenant should be done by admin portal
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
As per [1], tenant-conf.json changes done for customizing authorization header per tenant should be done by management console. But tenant-conf.json file is not accessible through management console now. It has to be done by adminportal at https://localhost:9443/admin/settings/advanced panel.So docs should be updated.
Suggested Labels:
Suggested Assignees:
Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked OAuth2 documentation section on customizing authorization headers per tenant, then verify the admin portal path at /admin/settings/advanced. Update the guidance so it reflects that tenant-conf.json changes are performed through the management console, and confirm the resulting instructions are consistent with the current portal workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100