04-25-2013 11:03 AM
Hi,
We trying to use permanent link like this one "http://localhost/nuxeo/nxdoc/default/5e84c7a3-e40c-4152-9497-b0cfdb916a6a/view_documents" to access document on a "nuxeo-cap-5.6-tomcat" server, with HF15 and DM add-on.
We first test this possibility with a default authentification: it works as expected (direct access).
But, we need use CAS authentication and in this case, the permanent link doesn't work anymore ... It's for us an important issue because we need direct acces on task (workflow context) send via email to our users.
Is it a known problem ?
We've done tests on two differents "Centos (5.9 and 6.4)" servers:
In both case:
On one server (Centos 6.4, nuxeo-5.6-HF10), after a first connection and deconnection (without removing JSESSION cookie) to the plateform, the direct access on a document works even with a CAS access for authentication (the return URL is correct). No error message are seen (with a default log4j configuration).
On the other one (Centos 5.9, nuxeo-5.6-HF15), an access after a first connection and deconnection (without removing JSESSION cookie) doesn't work and an error message is sent in the log:
2013-04-25 14:26:49,819 ERROR [org.nuxeo.ecm.core.api.CoreSession] Permission 'Read' is not granted to 'invite' on document /default-domain/workspaces/niv2/dd (5e84c7a3-e40c-4152-9497-b0cfdb916a6a - Folder)
2013-04-25 14:26:49,821 ERROR [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/nuxeo]] L'écouteur d'évènement de session (session event listener) a généré une exception java.lang.IllegalStateException: Please end the HttpSession via org.jboss.seam.web.Session.instance().invalidate()
at org.jboss.seam.contexts.Lifecycle.endSession(Lifecycle.java:221)
....
Thanks for your help
04-30-2013 12:00 PM
We just try nuxeo5.6-HF15 on a Ubuntu 11.10 machine and we got the same result
05-15-2013 07:01 AM
Hi,
05-15-2013 07:23 AM
Hi,
05-15-2013 10:46 AM
No, it's http
05-15-2013 10:58 AM
I thought about the nuxeo server.
05-17-2013 02:28 PM
I think it's more a nuxeo problem as the URL used to go to the CAS server for authentication, is a truncated URL.
05-22-2013 11:42 AM
I've tested this and it works correctly, the URL does not get truncated and after logging in on CAS I'm redirected to the correct page.
05-23-2013 12:17 PM
First, thank you for your help.
05-24-2013 01:29 PM
Yes, the second redirect is wrong, the service isn't encoded correctly, I'll try to give you a fix next week.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.