reshaprio/reshapr

As of today, we don't have guardrails to protect access to the Reshapr UI and API: once a user can authenticate to the configured internal IDP, then access to Reshapr is granted with the onboarding process being triggered. We talked with enterprise users and got the feedback that…

Currently, the Default Gateway Group (the one with ID 1) is created during the Flyway initialization migration with 2 labels: env: dev and team: reshapr. This Default Gateway Group is also listed in the shared resources set so that every user authenticated to Reshapr can actually…

As of today, when configuring the Reshapr authentication with your internal IDP / SOO, we don't provide a way to customize the scopes that are requested to the OIDC endpoint. Those scopes are openid, profile, and email. While those seem mandatory to access required user…