Changes
/* Diagnosis */
{| class="wikitable sortable"
|-
! width="200" | Test !! style="text-align:center" | Type !! Description
|-
| rowspan="3" width="200" | Try to find the service end point|| align="center"| [[File:IC_WebService_Diagnosis_Error.png| Error ]] || The service cannot be reached: Possible reason is an error in the web.config, which cannot be parsed. An other reason can be a faulty configuration of the service in IIS.
|-
| align="center"| [[File:IC_WebService_Diagnosis_Warning.png| Warning ]]|| The service end point provides a non-secure connection ("http://"). A connection without transport security should only be used for testing or in internal networks in a trusted enviroment only. This is generally not recommended for a productive environment.
|-
| align="center"| [[File:IC_WebService_Diagnosis_Warning.png| Warning ]]|| The service endpoint provides a secure connection ("https://") but has issues with the certificate provided: e.g. expired validity, non-trusted root authority etc. This means, a connection to the service will still be possible but it is not recommended to use in a productive environment.
|-
| Fetch a token || align="center"| [[File:IC_WebService_Diagnosis_Error.png| Error ]]|| The session management service is not configured to testing mode or does not have a valid test login configured in the {{UBIK}} database
|-
| Verify token || align="center"| [[File:IC_WebService_Diagnosis_Error.png| Error ]]|| The fetched token is not recognized as a valid token to be used with the content service. A possible reason is that the session management has a different database connection configured.
|-
| Verify if token gets invalid || align="center"| [[File:IC_WebService_Diagnosis_Warning.png| Warning ]]|| The fetched token is always valid. The reason can be that the setting "TokenRestrictive" is switched off which is not recommended for productive use.
|}
! Test !! Type !! Description
|-
| rowspan="3" width="200" | Try to find the service end point|| align="center"| [[File:IC_WebService_Diagnosis_Error.png| Error ]]|| The service cannot be reached: Possible reason is an error in the web.config, which cannot be parsed. An other reason can be a faulty configuration of the service in IIS.
|-
| align="center"| [[File:IC_WebService_Diagnosis_Warning.png| Warning ]]|| The service end point provides a non-secure connection ("http://"). A connection without transport security should only be used for testing or in internal networks in a trusted enviroment only. This is generally not recommended for a productive environment.
|-
| align="center"| [[File:IC_WebService_Diagnosis_Warning.png| Warning ]]|| The service endpoint provides a secure connection ("https://") but has issues with the certificate provided: e.g. expired validity, non-trusted root authority etc. This means, a connection to the service will still be possible but it is not recommended to use in a productive environment.
|-
| Fetch a token || align="center"| [[File:IC_WebService_Diagnosis_Error.png| Error ]]|| The session management service is not configured to testing mode or does not have a valid test login configured in the {{UBIK}} database
|-
| Verify token || align="center"| [[File:IC_WebService_Diagnosis_Error.png| Error ]]|| The fetched token is not recognized as a valid token to be used with the content service. A possible reason is that the session management has a different database connection configured.
|-
| Verify if token gets invalid || align="center"| [[File:IC_WebService_Diagnosis_Warning.png| Warning ]]|| The fetched token is always valid. The reason can be that the setting "TokenRestrictive" is switched off which is not recommended for productive use.
|}
! Test !! Type !! Description
|-
| rowspan="3" width="200" | Try to find the service end point|| align="center"| [[File:IC_WebService_Diagnosis_Error.png| Error ]]|| see the section in the Session Management tests
|-
| align="center"| [[File:IC_WebService_Diagnosis_Warning.png| Warning ]]|| see the section in the Session Management tests
|-
| align="center"| [[File:IC_WebService_Diagnosis_Warning.png| Warning ]]|| see the section in the Session Management tests
|-
| Add push data || align="center"| [[File:IC_WebService_Diagnosis_Error.png| Error ]]|| Adding push data failed. The reason could be a miscofigured service access point for the push service.
|-
| Fetch push data || align="center"| [[File:IC_WebService_Diagnosis_Error.png| Error ]]|| No push data received. If this error occurs even if adding the push data worked, the reason could be that the cached push data has been lost because the service had to be restarted or persisting the data in the background failed.
|-
| Reset push data || align="center"| [[File:IC_WebService_Diagnosis_Error.png| Error ]]|| see description of the possible error(s) described for "Fetch push data".
|}
