Onboarding Global Application
Prerequisites:
- You will need elevated permissions to perform most of these actions.
- Check out Authorization & roles for more info.
note
This will onboard either a global application or a context-type-specific global application, depending on the application's context type support.
- Ensure the application key (
appKey
) is readily available. This will be utilized during the Application activation process. - If not already there Go to the
Portal API URL
swagger page og the environment you want, se env table below. - navigate to:
POST: /api/portals/{portalId}/apps
- fill out the
portalId
andappKey
and press execute. - The app is now active in the given portal.
Make App Global
If your application is context-specific, meaning it's only available within one or more specific contexts, you can perform this process with an already onboarded application to make it global.
remember to leave the removeAppForContexts
true then.
ENV | Portal API URL | PortalID |
---|---|---|
feature | https://backend-fusion-project-portal-feature.radix.equinor.com/swagger/index.html | 5b43c3fd-77e3-4072-0aa1-08db310ee26d |
test | https://backend-fusion-project-portal-test.radix.equinor.com/swagger/index.html | 0177ef5f-c49e-4d2a-7907-08db31e4e851 |
prod | https://backend-fusion-project-portal-prod.radix.equinor.com/swagger/index.html | 24843980-c0bb-42ce-f082-08db31e659d1 |