nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

CMIS 1.1 browser bindings via share proxy

idwright

This seems like a rather simple question so apologies for asking but I can't find the answer.

I'm wanting to experiment with the CMIS 1.1 browser bindings via client side javascript in Share

For the deprecated CMIS interface the URL is:
Alfresco.constants.PROXY_URI + "cmis/p/…"

Going directly to Alfresco, i.e. not via Share, the URL is:
https://localhost:8080/alfresco/api/-default-/public/cmis/versions/1.1/browser/root/?cmisselector=children

Both of these work fine.

The question is how to access CMIS 1.1 via the share proxy?

(I believe the proxy
https://localhost:8444/share/proxy/alfresco/cmis/p/
maps to
https://localhost:8443/alfresco/s/cmis/p/
so the s or service part is different
)

Find more posts tagged with

Comments

kaynezhang

Why do you want to use share proxy? you can just send(GET/POST) request to alfresco repository directly using javascript.
The browser binding is designed to use just with HTML and JavaScript

idwright

It's necessary to use the proxy to avoid cross-site scripting limitations.
The legacy CMIS end points are supported via the proxy but I'd like to avoid using deprecated end points.
(Granted it's possible to work around this, how depends on the overall configuration, but examples using the legacy CMIS end points always seem to use the proxy so I thought it would be best to follow suit if possible)
Using the browser binding is to avoid the overhead of translating from XML to JSON.

I'm thinking about creating a CMIS based dojo data store which would be quite useful as it would easily plug in to lots of existing Dojo widgets (but like I said this is all experimental at this point - it would certainly be easier to do something more specific for the particular use case)

kaynezhang

You can use JSONP to bypass Same-Origin Policy,please look at http://docs.alfresco.com/4.2/pra/1/concepts/cmis-1.1-browser-binding-get.html

idwright

Thanks for the link
Like I said ways around it - I just thought I'd start by looking at options compatible with the deprecated CMIS api.

Undoubtably JSONP is the right way to approach this.

I think I'll take it that the answer to the original question is that there isn't a share proxy to the new CMIS endpoints .

kevinr

Thank you for raising this on JIRA also. We can add a Share proxy endpoint for CMIS 1.1 browser bindings so you should then be able to use the standard authentication mechanisms.

https://issues.alfresco.com/jira/browse/ALF-21129

Cheers,

Kevin

kevinr

I have tried adding an endpoint for the public API to Share Surf proxy config. I mapped "alfresco-public" to the public API REST URL on the Alfresco end so I could make calls like /cmis/versions/1.1/browser from Share.

However the authentication does not work nor can I find a simple way to map it across.

Looking deeper at PublicApiAuthenticatorFactory class (which is used to authentication the public API), it appears that it does not in fact support the various mechanisms that other endpoints support. It is quite strict, only supporting OAuth or X-Remote-User with a predefined X-Alfresco-Authenticator-Key from a list set in the repository. This is not easily done with the available authentication paths in Share currently.

So I cannot see a simple way to do this currently and it will require further investigation. I will try to make some time for it after the 5.0 release - as I find it very strange that the public API is different to the other endpoints in Alfresco! It does not make it easy to use unless you go the direct OAuth route…

softwareloop

I'm having the same issue while migrating a plugin from 4.2.f/5.0.a to 5.0.b. The plugin called the deprecated cmis API from javascript in the browser, via Share's proxy. In 5.0.b the deprecated cmis api is no longer available so I have to use the public alfresco/api. I'm experiencing the same problem as in the original post.

To do some experiments, I've also tried to add the endpoint as suggested:

<blockcode>
         <endpoint>
            <id>alfresco-public</id>
            <name>Alfresco public API - user access</name>
            <description>Access to Alfresco API that require user authentication</description>
            <connector-id>alfresco</connector-id>
            <endpoint-url>http://localhost:8080/alfresco/api</endpoint-url>
            <identity>user</identity>
         </endpoint>
</blockcode>

…but at the moment I'm stuck with 401 Unathorized responses.

idwright

The best I've managed so far is to obtain a ticket and append that to the CMIS URL as the alf_ticket parameter

There are various posts describing how to create a service that returns a ticket for a logged in user essentially:

get-ticket.get.desc.xml

<webscript>
   <shortname>Get current ticket</shortname>
   <description>Returns a valid ticket for the currently logged in user
   </description>
   <url>/auth/get-ticket</url>
   <format default="json" />
   <authentication>user</authentication>
   <transaction>none</transaction>
</webscript>
‍‍‍‍‍‍‍‍‍‍‍

get-ticket.get.js

model.sessionTicket = session.getTicket();
‍‍‍

get-ticket.get.json.ftl

<#escape x as jsonUtils.encodeJSONString(x)>
{
   "ticket": "${sessionTicket}"
}
</#escape>
‍‍‍‍‍‍‍

kevinr

Indeed I hit the same issues. It looks like it is going to need some changes before it can work.
1. Unfortunately the Public API does things a little differently as it is on a different endpoint with a different auth pattern.
2. Share/surf does not know how to Share auth between endpoints.

I am going to take a look at 1 & 2 to see what can be done for a Community release solution in the future.

Cheers,

Kevin

kevinr

Yes that is the best workaround for now - it is not ideal obviously and will not map nicely onto whatever SSO you are already using for Share - which is what we'd like to fix.

Cheers,

Kevin

idwright

Indeed - it would be great for this to work with SSO - to do this the CMIS endpoint needs to be able to use HttpServletRequest.getRemoteUser()

Cheers,
Ian

kevinr

Good news is that I have this working now on a branch. Ability to call Public API from Share and X-Alfresco-Remote-User SSO working against that API route. I will see what can be done about getting this into 5.0.c.

Thanks,

Kevin

kevinr

Unfortunately I am unable to get this into 5.0.c as it is already finalised and no more changes are allowed. So it will be in HEAD shortly after that, I'll let you know when there is a build to test.

kevinr

Hurrah. At last HEAD is open again and commits are merged, including the ability to call public APIs like CMIS from Share.
http://dev.alfresco.com/downloads/nightly/dist/

Share endpoint looks like this:

         <endpoint>
            <id>alfresco-api</id>
            <parent-id>alfresco</parent-id>
            <name>Alfresco Public API - user access</name>
            <description>Access to Alfresco Repository Public API that require user authentication. This makes use of the authentication that is provided by parent 'alfresco' endpoint.</description>
            <endpoint-url>http://localhost:8080/alfresco/api</endpoint-url>
            <identity>user</identity>
         </endpoint>
‍‍‍‍‍‍‍‍‍‍

Kev