Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

SPIKE: Provide estimate for RTR (Core Platform)

Description

Note: that is now addressed through a shared library: https://github.com/adamdickmeiss/folio-vertx-login

Please see epic for details.

Edge modules that require the login interface are:

  • edge-caiasoft

  • edge-connexion

  • edge-dematic

  • edge-inn-reach

  • edge-ncip

  • edge-oai-pmh

  • edge-orders

  • edge-patron

  • edge-rtac

Can RTR be handled in a single place (in edge-common) so that RTR doesn't need to be implemented separately in each of these modules?

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Steve EllisJanuary 18, 2023 at 2:52 PM

I'm closing this spike since you've provided the estimate in the comment of one sprint. There is another ticket for the actual work.

Adam DickmeissDecember 3, 2022 at 10:00 AM

Started looking at edge-common to determine if the API can be preserved.

https://github.com/folio-org/edge-common/tree/EDGCOMMON-57-RTR

It looks as it can be made backwards compatible. If that's the case, the work of updating edge-common to use folio-vertx-login can be implemented in one sprint.

Steve EllisDecember 2, 2022 at 5:50 PM

  would you be able to provide an estimate for the work required to change edge common to support RTR and update https://folio-org.atlassian.net/browse/EDGCOMMON-57#icft=EDGCOMMON-57 when you have a chance? We have a new goal to have all of the affected teams provide estimates.

Adam DickmeissNovember 14, 2022 at 3:50 PM

Yes. There would be a Token client specific for edge modules, based on the shared library.

Done

Details

Assignee

Reporter

Priority

Sprint

Development Team

Core: Platform

Parent

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 3, 2022 at 9:07 PM
Updated January 18, 2023 at 2:52 PM
Resolved January 18, 2023 at 2:52 PM
TestRail: Cases
TestRail: Runs

Flag notifications