How to preview D2-Smartview document with otds ticket?

lementree

Hi our D2-Smartview is integrated with OTDS, we try to access a document by calling the following link

https://<d2server>/D2-Smartview/ui/?redirect=false&docbase=<repository_id>#d2/nodes/<object_id>

this will redirect us to otds login and after login we can see the document

However we want to access this document without needing to signin with username and password

We have otds established with our solution, Can we access D2-smartview with OTDS ticket added to the url? or similar method

i know we can embed folderbrowser to view a folder, but we want to check on a specific document directly .

Thanks

Michael McCollough

The same should work with embed, use /D2-Smartview/ui/embed The embed function is something we have done a lot with internally and are looking to expose more for integration development. Please let me know if this helps.

Supported authentication scheme

The authentication scheme is defined in rest.security.auth.mode property of rest-api-runtime.properties in the classpath.

• basic-ct
  • Supports HTTP basic authentication and Client Token cookie for it
• ct-otds_token
  • Support OTDS integration with Documentum Server via token with Client Token cookie supported.
• ct-otds_ticket-otds_token
  • Support OTDS integration with Documentum Server. Checks Document client token first. If not available or valid, then check the OTDS ticket in the header "OTDS_TICKET". If not available or valid, then checks the OTDS OAuth token in the request.

Embed URL for D2 Smart View

• Embed URL query parameters and hash parameters must be URL encoded.

• Embed URL structure :  
  • Before D2 Smartview 22.2:: <PROTOCOL>://<HOST>:<PORT>/<D2SV_APP_CONTEXT>/ui/embed?<QUERY_PARAMS>#<HASH_PARAMS>
  • D2 Smartview 22.2 onwards:: <PROTOCOL>://<HOST>:<PORT>/<D2SV_APP_CONTEXT>/ui/embed?<QUERY_PARAMS>#d2?<HASH_PARAMS>

URL Parameters (M)-Mandatory/(O) - Optional

• URL query param: (Separated by & / key-value delimited by =)
  • docbase - (M) Docbase
    
  • application - (O) Application name
    
  • networklocation - (O) BOCS location
  • login - (O) Username for login user. Mandatory for a basic-ct authentication scheme.
  • password - (O) DM_TICKET from Documentum session. Mandatory for a basic-ct authentication scheme.
  • locale - (O) Application locale
  • accessible_compliant - (O)Default value is false. If value is true, then the accessibility compliant will be enabled inD2-SmartView.
  • client_location - (O)As embed application, D2-SmartView is expecting client location from origin application(Eg, latitude and longitude/ City and Country). The behavior of client location is driven by settings.properties. (M) when geolocation.enabled=true and geolocation.required=true
  • plugin_mode - (O) Forcing WSCTF as plugin mode.(Param value = wsctf/thin)
  • plugin_client_type - (O) This attribute is supproted when plugin_mode=wsctf. Type of client which runs D2 SmartView in embed mode.(Param value = browser/non-browser)
  • redirect - (O) Default value is true. If the value is set to false, then the login failure error message will be shown instead of redirecting to the sign-in page.
  • skip_data_cache - (O) Available on D2-Smartview 22.2.0 and later versions. Default value is false. If the value is set to true, then D2-Smartview UI will bypass the data caching feature and ensure data is always fetched from server. The local data caching feature is introduced since D2-Smartview 22.2.0 for delivering a faster UI navigation experience to the end users and it is enabled by default on supported browsers.
  • disable-sw - (O) Available on D2-Smartview 23.4 and later versions. Default value is false. If the value is set to true, then D2-Smartview UI will disable the data caching feature using Service Worker.

URL hash query param: (Separated by & / key-value delimited by =)

• id_source - (M) Defining operation source of operation (Example for Content Connect integration param value is CONTENT_CONNECT)

• otdsticket - (O) OTDS ticket for authentication. Mandatory for ct-otds_ticket-otds_token authentication scheme.

access_token - (O) OTDS token for authentication. Mandatory for a ct-otds_token authentication scheme.