Closed nsklikas closed 3 months ago
Frontend uses absolute paths for routing as well as for making calls to the backend API. This means that when the app is served behind a reverse proxy both the URLs used for routing and all calls to the backend do not work.
Bonus: Some api calls use an env var with an invalid path (https://github.com/canonical/identity-platform-admin-ui/blob/main/ui/src/api/client.tsx#L10) and some use a correct path that is hardcoded (https://github.com/canonical/identity-platform-admin-ui/blob/main/ui/src/api/identities.tsx#L9). It looks like that same is true for the rebac components (https://github.com/canonical/rebac-admin/blob/main/src/api/authentication/authentication.ts#L43)
Thank you for reporting us your feedback!
The internal ticket has been created: https://warthogs.atlassian.net/browse/IAM-911.
This message was autogenerated
Frontend uses absolute paths for routing as well as for making calls to the backend API. This means that when the app is served behind a reverse proxy both the URLs used for routing and all calls to the backend do not work.
Bonus: Some api calls use an env var with an invalid path (https://github.com/canonical/identity-platform-admin-ui/blob/main/ui/src/api/client.tsx#L10) and some use a correct path that is hardcoded (https://github.com/canonical/identity-platform-admin-ui/blob/main/ui/src/api/identities.tsx#L9). It looks like that same is true for the rebac components (https://github.com/canonical/rebac-admin/blob/main/src/api/authentication/authentication.ts#L43)