Service authentication

Cirrus Assessment Support Team -

Service authentication

In Cirrus, service security is provided in two aspects. First, transport level security by using HTTPS with trusted SSL certificate. Second, message-based authentication by using SOAP message security. You can use both of SOAP version. The following examples denotes how you can provide service credentials in your requests.

Example http-request for SOAP 1.1

POST https://svc.cirrusbeta.com/IMSLIS/PersonManagementService.svc/soap11 HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0/IPersonManagerSyncPortType/readPerson"
Content-Length: 1400
Host: svc.cirrusbeta.com
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)

<soapenv:Envelope xmlns:ims="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Header>
    <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
      <wsse:UsernameToken wsu:Id="UsernameToken-C6D431DE08F7A91864143798360264240">
        <wsse:Username>superSecretUsername</wsse:Username>
        <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">superSecretPassword</wsse:Password>
        <wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">rPfl0hVAi59YKoqiznE3Kg==</wsse:Nonce>
        <wsu:Created>2015-07-27T07:53:22.642Z</wsu:Created>
      </wsse:UsernameToken>
    </wsse:Security>
    <ims:imsx_syncRequestHeaderInfo>
      <ims:imsx_version>V1.0</ims:imsx_version>
      <ims:imsx_messageIdentifier>0123456789</ims:imsx_messageIdentifier>
    </ims:imsx_syncRequestHeaderInfo>
  </soapenv:Header>
  <soapenv:Body>
    <ims:readPersonRequest>
      <ims:sourcedId>fbdccaf5f5854a84be77731ab33166a5</ims:sourcedId>
    </ims:readPersonRequest>
  </soapenv:Body>
</soapenv:Envelope>

Example http-request for SOAP 1.2

POST https://svc.cirrusbeta.com/IMSLIS/GroupManagementService.svc HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: application/soap+xml;charset=UTF-8;action="http://www.imsglobal.org/soap/lis/gms2p0/readGroup"
Content-Length: 1600
Host: svc.cirrusbeta.com
Connection: Keep-Alive
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)

<soap:Envelope xmlns:ims="http://www.imsglobal.org/services/lis/gms2p0/wsdl11/sync/imsgms_v2p0" xmlns:ims1="http://www.imsglobal.org/services/lis/pms2p0/wsdl11/sync/imspms_v2p0" xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
  <soap:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
    <wsse:Security soap:mustUnderstand="true" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
      <wsse:UsernameToken wsu:Id="UsernameToken-C6D431DE08F7A91864143798174450130">
        <wsse:Username>superSecretUsername</wsse:Username>
        <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">
          superSecretPassword
        </wsse:Password>
        <wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">+3IG4FKAsy79hTDeQgmuEA==</wsse:Nonce>
        <wsu:Created>2015-07-27T07:22:24.501Z</wsu:Created>
      </wsse:UsernameToken>
    </wsse:Security>
    <ims:imsx_syncRequestHeaderInfo>
      <ims1:imsx_version>V1.0</ims1:imsx_version>
      <ims1:imsx_messageIdentifier>0123456789</ims1:imsx_messageIdentifier>
    </ims:imsx_syncRequestHeaderInfo>
    <wsa:Action>http://www.imsglobal.org/soap/lis/gms2p0/readGroup</wsa:Action>
  </soap:Header>
  <soap:Body>
    <ims:readGroupRequest>
      <ims:sourcedId>9c34d19065f74ca78e9b3cbce0343496</ims:sourcedId>
    </ims:readGroupRequest>
  </soap:Body>
</soap:Envelope>

Comments 0

Cirrus uses Zendesk to provide our Help Center services. Check out Zendesk's Terms of Service and Privacy Policy, as they govern your use of these services.

Powered by Zendesk