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.

Failure to authenticate

unknown-user

Folks,
Tried giving your product a whirl from a tomcat 5 install connecting to an Alfresco 3.4d (also tried 3.4e) installation (on a separate tomcat 6). Alfresco is working fine, connected the OW to the Alfresco as per the guide (wsdl in bootstrap file). Ensured validity of the WSDL urls directly in the browser with complete success - even the "WSDLACL" (as in: http://localhost:8080/alfresco/cmis/ACLService?wsdl) wsdl urls, even though the comment says '..currently not supported…'.
So, all set up and try to connect to Alfresco with any and all user/password combos (including the alfresco 'Admin' user) and get:
…
Caused by: com.wewebu.ow.server.exceptions.OwAuthenticationException: Login fail
ed: Wrong user name or password!
…
Caused by: javax.xml.ws.soap.SOAPFaultException: The message has expired (WSSecu
rityEngine: Invalid timestamp The security semantics of message have expired)
…

Find more posts tagged with

Comments

rapa

Hi Roger,
we are having a national holiday on Monday. On Tuesday someone from our team will look at your issue.
Happy Easter

Rainer

deko

Hi Roger,

have you already tried to log in with the ACL WSDL commented out anyway? As far as I know, this is still not supported by OpenWorkdesk (i.e. this is still not fully supported via CMIS). :ugeek:

As rapa said, we have national holiday today (easter monday), so I cant check this right now, but it will be the first task tomorrow morning :roll:

While checking this, I will also connect OWD against Alfresco 3.4e the same time, as I have not checked this yet… But this should be no problem at all…

So have a nice evening and be prepared to hear from the WeWebU team in a few hours.

deko

Hi Roger,

one thing i can tell you for sure, that this problem is definetely not caused by the ACL WSDL, as OpenWorkdesk is ignoring this WSDL ,if set. So the problem must be located somewhere else.

Where did you get Alfresco 3.4e? The latest version I can download from http://wiki.alfresco.com/wiki/Download_Community_Edition right now is 3.4d?

deko

Hi again,

so I setup the same scenario as yours, but I am still not able to reproduce this login failure. My steps were the following:

- I downloaded, installed and started Alfresco 3.4d (This is hosted in included Apache Tomcat 6)
- I downloaded Apache Tomcat 5 to host OWD
- I changed the default ports of this Tomcat 5 like described in the Quickstart Guide chapter 3.1, to avoid port conflicts with Alfresco´s Tomcat 6 instance, running on default ports
- I downloaded latest OWD Community Edition and copied the ow folder to the Tomcat 5 webapps folder
- I started the Tomcat 5 server without touching configuration, what made OWD run on top of the Alfresco cloud system (logged in successfully with user "admin" and password "admin")
- I stopped the OWD deployment by stopping Tomcat 5 and changed OWD WSDL configuration in owbootstrap.xml located under WEB-INF/conf/cmis to point to local Alfresco installation, with the ACL WSDL activated:

<WSDLRepository>http://localhost:8080/alfresco/cmis/RepositoryService?wsdl</WSDLRepository>
<WSDLNavigation>http://localhost:8080/alfresco/cmis/NavigationService?wsdl</WSDLNavigation>
<WSDLObject>http://localhost:8080/alfresco/cmis/ObjectService?wsdl</WSDLObject>
<WSDLMultifiling>http://localhost:8080/alfresco/cmis/MultiFilingService?wsdl</WSDLMultifiling>
<WSDLDiscovery>http://localhost:8080/alfresco/cmis/DiscoveryService?wsdl</WSDLDiscovery>
<WSDLVersioning>http://localhost:8080/alfresco/cmis/VersioningService?wsdl</WSDLVersioning>
<WSDLRelationship>http://localhost:8080/alfresco/cmis/RelationshipService?wsdl</WSDLRelationship>
<WSDLPolicy>http://localhost:8080/alfresco/cmis/PolicyService?wsdl</WSDLPolicy>
<WSDLACL>http://localhost:8080/alfresco/cmis/ACLService?wsdl</WSDLACL>
‍‍‍‍‍‍‍‍‍‍‍

- I startet Tomcat 5 once more and logged in successfully with my Alfresco admin user and the corresponding password

Can you please give more details about your environment so that I am able to reproduce this failure?
Which Java version do you have installed? Did you use latest OWD Community Edition which is 3.1.0.0 Final? Are you able to log in successfully, when using OWD on top of the Alfresco cloud system?

unknown-user

Hi again,

so I setup the same scenario as yours, but I am still not able to reproduce this login failure. My steps were the following:

…

Can you please give more details about your environment so that I am able to reproduce this failure?
Which Java version do you have installed? Did you use latest OWD Community Edition which is 3.1.0.0 Final? Are you able to log in successfully, when using OWD on top of the Alfresco cloud system?

Hi, thanks for taking a look at this. It looks very similar to what I've done; community install of 3.4e; did you try using against an Alfresco installation that has had the admin password changed? We must change default passwords of any software immediately after installation.
I didn't try against the cloud version, and yes I downloaded the latest version from the OWD website.

deko

Hi Roger,

I just downloaded Alfresco Community 3.4e (finally I found it here http://wiki.alfresco.com/wiki/Alfresco_Community_3.4.e_Download ), changed my admin password while installation and I am again able to connect to this new local Alfresco 3.4e installation via OpenWorkdesk Community Edition without having the authenticate failure reported by you.

My questions now:

- Do you have set any special characters in your password? Maybe you found an issue here. OpenWorkdesk should support all special characters and OWD just sends them via webservice to the Alfresco system. Maybe you set some special character which is/are not supported by this Alfresco service or is terminating the service. If you used special characters, try to set another password via the Alfresco UI (http://localhost:8080/alfresco) once more.

- Have you changed the user name too or is it still admin? While default installation of Alfresco, I think the user name cannot be changed at all and is "admin" by default after the installation.

- Can you connect to the Alfresco cloud, which should be actually Alfresco 3.4b. Username "admin" and password "admin". How to change configuration to connect OpenWorkdesk Community Edition against the Alfresco cloud is described in Quickstart Guide chapter 3.2.2.3. By checking this, we can ensure that you can connect to Alfresco in any way. If this connection works, the connection to your local Alfresco must work too, as tested by me right now with Alfresco 3.4e.