Access resource servers in Push

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
api, authentication, backend

Research direction

Read the linked Manage issue 445 and trace the Push flow that currently sends Resource Servers as RPs with the isResourceServer metadata field. Determine how Resource Servers and RPs should be represented as separate types with distinct fields. Done means the Push behavior no longer relies on that extra metadata field and sends the appropriate type for each resource.

Written by the indexing model from the issue text.

Description

not-ready

See https://github.com/OpenConext/OpenConext-manage/issues/445

Currently, Manage pushes Resource Servers as RPs with an extra metadata field isResourceServer set to true. This is kind of hackish; we probably want to distinguish betwene them on a higher lever, and send them as different types with different fields.

Needs refactoring.

Dominant language
Java
Stars
4
Forks
6
Avg merge
5d 32m
Merged PRs (30d)
3

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.

More from OpenConext/OpenConext-oidcng

All issues in OpenConext/OpenConext-oidcng

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.