Changes
== Diagnosis ==
In the top section, the links to the connected services (Content, Session Management, and Push service) are shown. These can be also be tested by the user clicking the links manually, these connections will are also tested automatically while the test runs. The following steps tests are tested to executed check the functionality of the web service. The details of each test run can be shown by clicking on the "Details..." link in the results list.
==== 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.
* 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 ====
* Try to find the service end point
** (see the same section in the session management tests above)
* Check database connection
** Error: Database cannot be reached. Possible reason can be a faulty database connection string or the used database server cannot be reached or is blocked by the network configuration.
* Upload a file
** Error: The configured target file system in the database settings is not set correctly to a folder allowing to write data. The reason can be that the user running the {{UBIK}} web service does not have read/write access to the configured target folder.
* Download a file
** Error: The uploaded file (uploaded in the previous test) cannot be downloaded. Possible reasons could be a timeout which is set too restrictive to download the data in time.
* Write logs
** Error: The log cannot be written. Possible reason is that the configured log folders do not exist or the user running the web service has no read/write access to the logging folder.
* Check rights structure
