SuperOffice Online is an online platform serving thousands of customers and, like any serious distributed and federated platform service, it requires several phases for development, testing and production. SuperOffice provides three environments: development, stage and production.
The development and stage environments are essentially an isolated copy of production. Each environment has it's own Operations Center (OC), app store, SuperId, customer tenants, and partner apps.
This means applications must be prepared to operate in at least two environments prior to being listed in the public app store for paying customers.
Why Different Environments?
It's really quite simple: security. SuperOffice takes security very seriously, while at the same time makes it easy for applications to transition from one environment to the next when ready.
The separation also prevents applications still in development from accidentally being used in stage and production environments.
After registration, every application receives it's own set of dependencies, including: application identity, application token, and environment specific certificates.
These dependecies are explained in Application Registration. If you have not already read that, please go ahead and do that now.
There are two additional settings that must be defined for each application and they are:
- SoFederation Gateway (SuperId)
- certificate thumbprint identifier
This is the URL to the SuperOffice federation authentication provider, otherwse referred to as SuperId.
SuperOffice Certificate Id
This defines the thumbprint identifier for the certificate used in security token validation. Security token validation is explained in more detail in Security and Authentication.
Different phases of development require different environments for hosting and serving up partner applications. It is crucial to understand these settings to manage applications accordingly.