Change Request: Improve SSI Link Invitation Summary in OpenConext-dashboard
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- backend
Research direction
Start by locating the SSI Link Invitation summary generation and Jira ticket creation entry point in OpenConext-dashboard. Check how the IdP's OrganizationName:en and entityID are supplied to the summary and custom fields. Done means the subject uses the English organization name in the requested format while the entityID remains in the custom fields.
Written by the indexing model from the issue text.
Description
Change Request: Improve SSI Link Invitation Summary in OpenConext-dashboard
Currently, an SSI Link Invitation uses a summary such as:
New invite connection for IdP https://sts.windows.net/a77b0754-fdc1-4a62-972c-8425ffbfcbd2/ to SP ibron-frontend.surf.nl
This summary is shown in Jira. The issue is that the entityID of the IdP (e.g. https://sts.windows.net/a77b0754-fdc1-4a62-972c-8425ffbfcbd2/) is not human-readable. Since many IdPs now use Azure, their entityIDs are long, opaque URIs that do not show which institution the ticket concerns.
This results in unnecessary extra work for the support team handling these tickets (e.g. looking up the entityID, opening the ticket to determine which institution it refers to, etc.).
Requested Change
Please modify the generated summary (subject) of the SSI Link Invitation ticket so that it includes the OrganizationName:en of the IdP instead of the entityID.
Example of desired format:
New invite connection for IdP ‘Saxion University of Applied Sciences’ to SP 'IBron frontend'
The entityID should still be included in the custom fields and may remain unchanged there.
- Dominant language
- JavaScript
- Stars
- 8
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from OpenConext/OpenConext-dashboard
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Export stats pdf and png not workingMay be free again @oharsta claimed this 141 days ago, and no pull request is open. Open
OpenConext/OpenConext-dashboard#687 · 1 assignee ·
-
Create banner to show service informationMay be free again @oharsta claimed this 198 days ago, and no pull request is open. Open
OpenConext/OpenConext-dashboard#685 · 1 assignee ·
All issues in OpenConext/OpenConext-dashboard
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
srikanth235/centraid#1155 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
microsoft/monaco-editor#5563 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day