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.
The Kerberos addon makes Nuxeo Drive account creation fail.
In previous client (2.0.0.0522), registering the client worked with or without kerberos module in the server. So installing that version and then upgrading to 2.0.818 is a possible workaround.
The problem is that creating an account in a Nuxeo server without Kerberos generates this requests http://nuxeoserver.com:8080/nuxeo/drive_login.jsp?applicationName=Nuxeo+Drive&forceAnonymousLogin=true&deviceDescription=Windows+Desktop&deviceId=XXXX&permission=ReadWrite
Server responds with a 302 and a new requests is made: http://nuxeoserver.com:8080/nuxeo/login.jsp?deviceDescription=Windows+Desktop&forceAnonymousLogin=true&permission=ReadWrite&requestedUrl=drive_login.jsp%3FapplicationName%3DNuxeo%2BDrive%26forceAnonymousLogin%3Dtrue%26deviceDescription%3DWindows%2BDesktop%26deviceId%XXXX%26permission%3DReadWrite&deviceId=XXXXb&applicationName=Nuxeo+Drive
After setting our credentials in the form, that registration is complete and the syncronization starts.
However, when kerberos is enabled, the response to the first request is a 401 and the second request is just http://nuxeoserver.com:8080/nuxeo/login.jsp
And after write our username and password we are redirected to Nuxeo main page instead of registering our Nuxeo Drive client.
I've just found it is solved in 7.3: https://jira.nuxeo.com/browse/NXP-16791
Is it planned to be patched for 6.0?
Thanks.
Perfect then.
I have to do more testing but after applying the patch it appears that Nuxeo Drive still does not login properly.
