OTCSTICKET from OTDS API?

Is it possible to obtain an OTCSTICKET to use with the CS REST API by authenticating with OTDS REST API? I have been able to obtain the OTDSSSO token from the OTDS API and convert that using the ValidateUser operation of the CWS Authentication service but dont see an obvious way to achieve the same result for OTCSTICKET

Find more posts tagged with

Comments

Dave Carpeneto

Hiya - you can pass the OTDSTicket to the CS REST API calls without issue. You'll notice that when you use OTDSTicket the CS REST call returns the response will include a OTCSTicket value. From that point on you can use either OTCSTicket or OTDSTicket values - either work (however the OTCSTicket token is processed more efficiently).

Note that if you're using OTDSTicket the header name is also OTDSTicket, and for OTCSTicket it's OTCSTicket.

Ferdinand Prantl

You cannot get the OTCS ticket from OTDS. You can get it from CS by "POST .auth", or from CS by issuing a request authenticated by any means (usually by OTDSTicket) and reading the value of the "OTCSTicket" response header.

If you already have the OTDS SSO ticket, you can get the OTDS ticket for CS REST API by an additional call to OTDS. (SSO ticket is usually once-use only.)

Request:

POST /otdsws/rest/authentication/resource/ticketforuserContent-Type: application/json{ "targetResourceId": "CS resource ID", "userName": "user name", "ticket": "OTDS SSO ticket"}

Response:

Content-Type: application/json{  "ticket": "OTDS ticket for CS"}

However, you can use the OTDS SSO ticket for the very first CS REST API request right away. No need to request the resource-specific ticket from OTDS. The usual scenario is to authenticate the very first call with OTDSTicket and then switch for the OTCSTicket, which comes back always fresh from CS in the "OTCSTicket" response header. You should switch even the resource-specific OTDS ticket for the OTCS ticket after the first call, because validating OTDS ticket is more expensive in CS. It needs a round-trip to OTDS.

Keanep

Quoted Ferdinand Prantl on 05/21/2018 10:26 AM:

Thanks for responding. Can I ask, in the scenario you describe above, how is the request to the CS REST API assembled to include the OTDSSSO token? Would I just include OTDSSSO as a header attribute with the full OTDSSSO token as the value?

Ferdinand Prantl

OTDS ticket has to be passed in a request header, as any supported authentication ticket. The header is called OTDSTicket in this case.

Request:

GET ...CGI.URL.../api/v1/authOTDSTicket: ...OTDS.ticket...

Response:

Content-Type: application/jsonOTCSTicket: ...fresh.OTCS.ticket...{...authenticated.user.information...}

In a similar way you would pass OTCS ticket in the OTCSTicket header, once you have it:

Request:GET ...CGI.URL.../api/v1/volumes/141OTCSTicket: ...OTCS.ticket...

Response:

Content-Type: application/jsonOTCSTicket: ...fresh.OTCS.ticket...{...enterprise.volume.information...}