microsoft / microsoft/AzureTRE
`make-auth` generates client secrets in a legacy way?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Describe the bug
Running make-auth creates application registrations with client secrets, however, these client secrets are not shown in the Entra ID UI for app registrations. This makes me wonder if the process uses a legacy method.
If it uses a legacy method, it should be updated to use a current method, which would make it easier to rotate the secrets.
Azure TRE release version (e.g. v0.14.0 or main): v0.17.0
Contributor guide
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 by locating the implementation of the make-auth command and inspect how it creates Entra ID application registrations and client secrets. Compare that process with the current method for creating rotatable secrets; the work is done when newly generated secrets are visible and manageable in the Entra ID UI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- authentication, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100