Skip to main content

WCF/SOAP Authentication (Obsolete)

warning

This authentication method is obsolete. For current authentication methods, please refer to the Authentication documentation.

Use of WCF services / SOAP channel​

In cases where an integration must be carried out using SOAP methods, it is necessary to make calls to the legacy system.

Such authentication, which can be performed via both REST calls and SOAP WCF calls, returns a valid token to be used for subsequent requests.

The submission of an authentication request is documented via Swagger at the link

/swagger/ui/index#!/UserAuthentication/UserAuthentication_BasicAuthentication

Authentication can be performed by calling the service.

PRODUZIONE: [POST] https://cct-wcf.teamsystem.com/knos/wcf/CS/api/UserAuthentication/BasicAuthentication

TEST: [POST] https://cct-wcf-test.teamsystem.com/knos/wcf/CS/api/UserAuthentication/BasicAuthentication

During the authentication process on the SOAP service, the TS Archive access credentials (username and password) must be provided. Alternatively, if the client has already been activated and migrated to the Digital portal, application credentials obtained from the Digital portal must be provided.

They are not required.

The Content-Type must be application/json

Body​

The request body must have the following format:

{
  "UserName": "string",
  "Password": "string",
  "Options": [
    {
      "Name": "string",
      "Value": "string"
    }
  ]
}
  • Username: It contains the username of the account that needs to log in
  • Password: It contains the password of the account selected for login.
  • Options: They are not required and are reserved for future implementations.

Responses​

The operation is successful if and only if the HTTP response code is 200. Any other response code indicates an error state

HTTP 200​

The operation has been completed successfully and the SecurityToken is issued to be used for authentication in subsequent REST API calls. The password expiration date should also be considered, as it represents the PasswordExpirationDate.

It is essential to evaluate the PasswordExpirationDate, since if it represents a date earlier than the current date, it implies that the issued token is valid only for performing a password change. In this case, rely on the portal and the front-end pages to change the password. Any calls made with a token issued from an expired password will result in an error.

Response body:

{
  "UserIdentity": {
    "SecurityToken": "string",
    "PasswordExpirationDate": "2022-02-14T08:48:20.753Z"
  },
  "ServiceInfo": {
    "ServiceVersion": "string",
    "Info": [
      {
        "Name": "string",
        "Value": "string"
      }
    ]
  }
}

HTTP 400​

One or more parameters provided in the request are incorrect, or required parameters are missing.

{
  "code": 400,
  "status": "BADREQUEST",
  "error": "BadRequest",
  "message": "I parametri username e password sono obbligatori",
  "timestamp": "2022-02-14T12:20:47.9466829+01:00"
}

HTTP 401​

The provided credentials are not correct.

{
  "code": 401,
  "status": "UNAUTHORIZED",
  "error": "Unauthorized",
  "message": "Username o password errati.",
  "timestamp": "2022-02-14T10:45:44.1219662+01:00"
}

HTTP 500​

The server encountered an unexpected error while processing the item creation request. If the problem persists, please contact support.