Repository navigation
Multi tenancy support for Consent Portal and VITE_ORG_ID #73
Description
Portal currently relies on VITE_ORG_ID in the env for org ID. This environment variable is required for certain features, such as displaying only the org-wide purposes, as this requires the org ID to be passed in as the group ID to the purpose search api.
It is probably better to remove VITE_ORG_ID from the portal frontend and implement a more sophisticated design for multi-tenancy
Activity
rashmithachamikara commentedon Aug 4, 2026
#81 Introduces /me endpoint
Portal does not rely on env for VITE_ORG_ID anymore, as it now takes this from /me of BFF. The env value has been removed
rashmithachamikara commentedon Aug 4, 2026
@anjuchamantha, although the org ID is obtained from the BFF and removed from the frontend env, the portal URLs do not show the org ID, unlike in Asgardeo consoles. Please create an issue if this feature is needed as well.
For end users, this might not be required, but this might be required for SAAS admins managing different organizations.
anjuchamantha commentedon Aug 4, 2026
Hi @rashmithachamikara
Thanks you for raising this. We'll look into the multi-tenant scenarios separately. Hope for a single tenant usecase there are no issues.
Thanks,
Anju.