Changes

WebService Diagnosis

114 bytes added, 10:30, 30 April 2015
/* Session Management */
==== Session Management ====
* Try to find the service end point
** 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.
** 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.
** 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.
* {| class="wikitable sortable"|-! Test !! Result type !! Description|-| rowspan="3" | Try to find the service end point|| 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.|-| 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.|-| 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** || 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** || 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** || 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.|}
==== {{UBIK}} Content Service ====
10,686
edits