![]() The HTTP request body should contain one element, with zero, one, or more XIMSS protocol requests. Where sessionID is the session message urlID attribute. HTTP Synchronous Communications A client should send requests to a created XIMSS session use the following Session URL: This method is useful if an application first retrieves an HTML page or some other documentįorcing the browser to ask the user for credentials, and then the application creates a XIMSS session for the same user,Īs the browser will resend the same credentials when sending a request to the /auth/ximsslogin/ URL. The response is a element containing the requested operations result.Īlternative URLs can be used to start a XIMSS session using the TLS Client Certificate, The Server sends an HTTP response with XML data. The XML body should contain one element containing zero, one, or several XIMSS Pre-Login operations. In this case, no login operation is performed. This functionality is the same as the WebUser Interface Automatic Login and Single Sign-on functionality,Ī request to the /ximsslogin/ URL can contain a text/xml body. The TLS Client Certificate (if specified), or using the HTTP authentication metods. If the userName parameter is absent, the Server tries to authenticate the request using If the errorAsXML parameter is present and the login operation fails, the error condition is returned not as an HTTP result code with an HTML error page,īut as an element with errorNum and errorText attributes,.If the sessionid parameter is present, the SessionID method is used.The request must contain the authData parameter contaning the base64-encoded CRAM-MD5 "challenge response". The "nonce" parameter value should be a value received as part of a features response (see below), it should be a valid "authentication nonce". If the nonce parameter is present, the CRAM-MD5 method is used.If the password parameter is present, the regular clear-text method is used.domainName/ximsslogin/ If the request contains the userName parameter, the Server tries to authenticate the specified user (Account): HTTP Login To start a XIMSS session, a client application should send an HTTP request to the CommuniGate Pro HTTPU module If a request produces a non-empty response body, the body is always an XML text containing one element,Īnd the response Content-Type header field is text/xml. If a request contains a body, it is assumed to be an XML text, unrelated to the actual value of the Content-Type header field. Responses from the session using HTTP requests.Ĭlient applications can use GET and POST HTTP requests. When a XIMSS session is created, the client application can send XIMSS protocol requests to it and receive XIMSS protocol XIMSS Connections to Other ModulesĪ client application can access the XIMSS interface via HTTP connections.Ī client application should start by sending an HTTP Login request to create a new XIMSS session. Follow the Listener link to tune the XIMSS Listener. If thereĪre too many incoming connections open, the module will reject new connections,īy default, the XIMSS module Listener accepts clear text connections on the The number of simultaneous connections the XIMSS module can accept. In order to communicate with your Server. Module starts to accept all XIMSS connections that clients establish Setting, the XIMSS module creates a Listener. When you specify a non-zero value for the Maximum Number of Channels The XIMSS module records in the System Log are marked with the XIMSSI tag. Otherwise your System Log files will grow in size very quickly. When the problem is solved, set the Log Level setting to its regular value, Info: in this case protocol-level or link-level details will be recorded You may want to set the Log Level setting to Low-Level or All But when you experience problems with the XIMSS module, (message transfer reports) or Problems (message transfer and non-fatalĮrrors) levels. Use the Log setting to specify the type of information the XIMSS Open the Access page in the Settings realm: Use the WebAdmin Interface to configure the XIMSS module.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |