| Note |
|---|
|
Note that this page has been deprecated; the information it contains is no longer current. It has been retained for historical purposes only. |
| Div |
|---|
| style | float:right;margin-left:1em;margin-bottom:1ex |
|---|
|
| Note |
|---|
This page was last updated on February 27, 2017. |
|
...
Summary of errorURLs in IdP Metadata
| Advanced Tables - JSON Table |
|---|
| paths | $ |
|---|
| enableHeadingAttributes | false |
|---|
| enableSorting | false |
|---|
| autoTotal | true |
|---|
| headingAugments | IdP Category, # of IdPs |
|---|
| script | ^local-idp-error-url-summary.json |
|---|
|
|
As a service to the community, InCommon Operations regularly probes errorURLs in IdP metadata. The results of the latest probe are recorded in the table below. Your IdP is good to go if all of the following are true: 1) your IdP metadata currently includes an errorURL, 2) the curl error code is 0, and 3) the HTTP response code is 200. If your IdP metadata does not include an errorURL, or the one you have listed in metadata is not working properly, please update your metadata today!
...
| Tip |
|---|
| title | How to navigate this page |
|---|
|
| Click a column heading to sort on that column. Use your browser's Find command to search this page. |
| Advanced Tables - JSON Table |
|---|
| fieldPaths | OrganizationName,entityID,errorURL,curlExitCode,HTTPResponseCode |
|---|
| sortColumn | Organization Name |
|---|
| paths | $ |
|---|
| autoNumber | true |
|---|
| headingAugments | Organization Name,IdP Entity ID,Error URL,Curl Exit Code,HTTP Response Code |
|---|
| script | ^local-idp-error-url-list.json |
|---|
| sortIcon | true |
|---|
|
|