OpenConext / OpenConext/OpenConext-access

Give user info on when Application is published on platform and activated for IdP

Open
#950 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

nicetohave
Dominant language
JavaScript
Stars
4
Forks
0
Avg merge
1d 14h
Merged PRs (30d)
22

Description

Image Image

New Feature Request

Summary

Problem: What is the pain point? (e.g., "Users cannot filter results by date.")
Now, we cannot show the user when an app has been published on the platform, or when app has been activated for their institution.

Value: Why should we build this? (e.g., "Improves data accessibility for
power users.")
It's nice to show how long an app has been on the platform, and it's nice to show a user when the activation has taken place (how long has my institution been connected to this app)

Proposed Solution

For “date added,” this would require a migration in Manage to also store the date of the first revision in the latest revision and copy it to every new revision.

For “date activated,” this would require a migration in Manage to determine and track, for each allowed-entity, when it was added. This affects quite a few systems.

For “date published,” this would require a migration in Manage to track when the state changed from “testaccepted” to “prodaccepted,” as well as a migration to determine this for all existing SPs and RPs and copy it to each new revision.

Developer Checklist

To be completed by the developer during implementation.

Testing and QA

Describe how to verify and test this change.

Test Environment and Setup
  1. Point to [URL/Branch]
  2. Use account with [Role/Permissions]
Test Checklist
  • Happy Path: Feature works as intended under normal conditions.
  • Edge Case: [Describe specific test item]
  • Validation: [Describe specific test item]
  • UI/UX: Verified layout across screen sizes.

Extra Information

Add any other context, related issues, or technical notes here.

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 tracing the Manage data for revisions, allowed entities, and the transition from “testaccepted” to “prodaccepted.” Determine how existing records can be migrated and how the resulting dates should reach the user-facing application view; done means users can see when an app was added, published, and activated for their institution, with migration and QA coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.