| Section |
|---|
| Column |
|---|
|
We have a test and production environment your service can connect with. You will start with defining your service in our Test environment, to verify it works as expected. This environment is standardized and in close alignment with the production environment. After you have requested to publish the service to production and if we confirm all requirements are met, such as the necessary contracts and TLS requirements, we will accept the service to be deployed to our Production environment making it available to all users of SURFconext. This page outlines the differences between these environments.
SURFconext Ecosystem
|
| SURFconext Test |
| SURFconext Production |
|
|
...
| Test mode | Production mode | - Environment for testing purposes only
- Test with test/diy ldP or institution's test ldP's
- Do not use (privacy) sensitive information
- No contract necessary
- New SP's can be configured via Selfservice SP Dashboard
|
|
|
...
- Uses specific ldP metadata (see below)
|
|
|
...
- For short staging testing before going to production
- Staging ldP's available only
- Uses specific ldP metadata (see below)
This environment will be discontinued at July 1, 2019
- No SLA
- Every IdP is by default connected to every available SP and the way around
| |
|
|
...
| Info |
|---|
Please note that SURFconext acts as an identity provider to services and is the only IdP a service connects to. That is why you use the IdP Metadata links as stated in the table above. |
SURFconext Test environment- For testing purposes only.
- Test with the SURFconext test IdP's or institutions test IdP's (
|
|
...
- if available) that have fictitious accounts.
- No contract necessary.
- Do not use (privacy) sensitive information
- New SP's can be configured via Selfservice SP-Dashboard.
- SAML
|
|
...
- Specific IdP metadata needed that refers to and connects with the SURFconext test environment.
- OpenID Connect: specific .well-known endpoint that refers to our test environment.
SURFconext Production environment |
|
The Production environment consists of two sub-environments: a Staging and a Production mode. IdP's and SP's configured in the Staging mode cannot connect to Production mode and vice versa.
Staging mode
- For short staging testing, before going to production
- Test IdP's available only
- SAML: Specific IdP metadata needed. This is the same metadata end-point as in Production, see below.
Note: The staging environment will be discontinued at July 1, 2019
Production mode
...
- Contracts need to be in place
- Holds privacy sensitive information from institutional users
- Production IdP's available only.
- Meet the SSL/TLS Requirements as stated on this page for both SP's and IdP's. You will need an SSL Labs Rating B or Higher.
- SAML Specific IdP metadata needed that refers to and connects with the SURFconext production environment.
|
|
...
...
- that refers to our production environment.
Actions IdP's can take to test servicesSome Institutions/IdP's want to test services before a service is connected in Production Mode, with identities the institution controls |
|
...
. Institutions that want to |
|
...
do so are recommended to configure a test IdP and request the SURFconext team to connect that test IdP to the SURFconext test environment. |
|
...
| Column |
|---|
| Navigate | Page Tree |
|---|
| root | Documentation for Service Providers |
|---|
| searchBox | true |
|---|
|
|
|