Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API location migration #308

Open
phavekes opened this issue Sep 16, 2024 · 7 comments
Open

API location migration #308

phavekes opened this issue Sep 16, 2024 · 7 comments
Assignees
Labels
Milestone

Comments

@phavekes
Copy link
Member

Move alle API endpoint that are not used by our own frontend to /api/external/v1/**

This needs to be done in two steps:

  1. support both locations to migrate other users
  2. disable old path's in Openconext-Invite
@oharsta
Copy link
Member

oharsta commented Sep 16, 2024

This affects the following API's

"/api/voot/**",
"/api/external/v1/voot/**",

"/api/teams/**",
"/api/external/v1/teams/**",

"/api/profile/**",
"/api/external/v1/profile/**",

"/api/aa/**",
"/api/external/v1/aa/**",

"/api/deprovision/**",
"/api/external/v1/deprovision/**",

@phavekes phavekes added this to the 0.0.22 milestone Sep 16, 2024
@oharsta
Copy link
Member

oharsta commented Sep 17, 2024

@Tyskai See https://aa.test2.surfconext.nl/authorities for the AA overview

@oharsta
Copy link
Member

oharsta commented Sep 17, 2024

For the actual values used in the Java apps, you can ssh to [email protected] and see the application.* files in /opt/openconext/

@thijskh
Copy link
Member

thijskh commented Sep 25, 2024

AA is done

@phavekes phavekes modified the milestones: 0.0.23, 0.0.24 Oct 29, 2024
@thijskh
Copy link
Member

thijskh commented Nov 13, 2024

All apps are done. The /api/voot compat location and the legacy paths in the SecuriyConfig can now be removed

@oharsta
Copy link
Member

oharsta commented Nov 19, 2024

@Tyskai Can you confirm that the following endpoints are not used by any of external applications identified by the endpoint name?

"/api/voot/**",
"/api/teams/**",
"/api/profile/**",
"/api/aa/**",
"/api/deprovision/**",

Only checking in ansible is not enough, as this does not prove that the actual production instance is not using the old url.

@thijskh
Copy link
Member

thijskh commented Nov 19, 2024

@Tyskai Just check the haproxy access logs I guess?

@oharsta oharsta modified the milestones: 0.0.25, 0.1.0 Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Backlog
Development

No branches or pull requests

4 participants