...
| Status | Color | Description |
|---|
| ERROR | Red | - The IdP's response contains an HTTP Error or the web page returned does not look like a login page. The most probable causes for this error are HTTP errors (e.g.: 404 error)
- The IdP most likely does not consume the eduGAIN metadata correctly or it hasn't returned a web page that looks like a login form.
A typical case that falls into this category is when an IdP returns a message "No return endpoint available for relying party" or "No metadata found for relying party". - The IdP has a problem with its SSL certificate.
|
| OK | Green | - The IdP most likely correctly consumes eduGAIN metadata and returns a valid login page. This is no guarantee that login on this IdP works for all eduGAIN services but if the check is passed for an IdP, this is probable.
|
| DISABLED | White | - The IdP is excluded because it cannot be checked reliably. The "Page Source" column, when an entity is disabled, shows the reason of the disabling.
|
On-line interface parameters
| Parameter name | Example |
|---|
date | date=2020-02-20 |
reg_auth | reg_auth=https://reg.auth.example.org |
idp | idp=https://idp.example.org/idp/shibboleth |
status | status=ERROR |
Example:
https://technical-test.edugain.org/eccs2?reg_auth=http://www.idem.garr.it/&date=2020-11-10&status=ERROR
JSON interface
The eduGAIN Connectivity Check service 2 provides a JSON feed on the monitoring results.
...
