device-management-toolkit / device-management-toolkit/sample-web-ui
Need "Verification" on UI of Enterprise Activation Method (TLS Enterprise) with OAMTCT console
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 19
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 49
Description
Describe the feature enhancement request
When using RPS/RPC to activate TLS Enterprise mode, need to be able to "Verify" or validate that the device being activated was indeed activated. Otherwise, activating in the dark and not knowing if it was successful.
To Reproduce 🪜
Activate a platform with TLS Enterprise mode (NON CIRA)...
Expected behavior
RPC to send back "Activation Status" or Activated or Failed... etc...
Screenshots 🖼️
AMT Device (please complete the following information): 🖥️
N/A
Service Deployment (please complete the following information): ⛈️
N/A
Additional context
Add any other context about the problem here.
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
No files or tests are named. Start by tracing the RPS/RPC flow used to activate TLS Enterprise mode in the Angular UI, then determine how the activation result can be surfaced. Done means the UI reports whether activation succeeded or failed, including for the non-CIRA case described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100