CS Widgets II

Hi,

as I did not have a single suggesting from my previous post, let me try again with a slightly different approach. We are using CS Widgets and trying to follow the sample provided by OpenText in the Getting Started of the Widgets documentation (https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=57082486&objAction=browse&viewType=1).

We know the correct location of the widgets and after solving problems such as the CORS and others we were finally able to move forward. We are using OTDS for the Content Server, and when running the sample, provided (code below) we get an authentication window, we are not sure where it is coming from or even worse, able to successfully pass it.

enter image description here

Any suggestions?

CODE ------------------------------------------------------------------------------------

          var connector = new csui.util.Connector( {
              connection: {
                  url          : "http://servername/livelink/livelink.exe/api/v1/",
                  supportPath  : "/img"
              }
          }),

        // Create the container browsing widget.
        browser = new csui.widget.FolderBrowserWidget( {
              connector  : connector,
              placeholder: "#folderBrowser"
        });

END CODE ------------------------------------------------------------------------------------

Find more posts tagged with

API

Comments

Ferdinand Prantl

You did not provide any authentication ticket, that's why the widgets fall back to the login dialog. (The usual scenario is to use SSO. The widgets are embedded in a portal and they are supposed to be given OTCSTicket, OTDSTicket or other header acceptable by the CS, to avoid the fallback dialog.)

What error do you see at the browser console when you submitted the credentials?

Manuel Guerreiro

Thanks Ferdinand for the info. It is really appreciated, believe me. It is unfortunate though that the sample from which the code was copied does not mention anywhere the requirement for the authentication ticket (even though in hindsight makes all the sense).
As I mentioned in my previous post (Previous post) what we really get is a CORS error and underneath there is a 403 - Forbidden; The reason, right now, I believe it is because we are getting a Access-Control-Allow-Origin' header contains multiple values, which is not allowed. But once again, thanks for the tip.

Ferdinand Prantl

True, the code samples showing do not include it, because they usually concentrate on their topic and omit the authentication possibilities. I admit that the documentation does not emphasize it enough. On the other hand, it is not a bug. For example, the first version of OT AGA was released depending on the built-in login dialog. And we use it a lot during the development too.

You should not configure any CORS headers on the front end web server. The <LLCGIURL>/api/... requests always add them into responses to AJAX requests.