OpenConext / OpenConext/OpenConext-dashboard

Change Request: Improve SSI Link Invitation Summary in OpenConext-dashboard

Open
#679 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
8
Forks
2
PR merge metrics
No merged PRs in 30d

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.