Maven authentication error (Error code 401)

We tried to make OpenKM as intuitive as possible, but an advice is always welcome.
Forum rules
Please, before asking something see the documentation wiki or use the search feature of the forum. And remember we don't have a crystal ball or mental readers, so if you post about an issue tell us which OpenKM are you using and also the browser and operating system version. For more info read How to Report Bugs Effectively.
Post Reply
ncarp
Fresh Boarder
Fresh Boarder
Posts: 5
Joined: Thu Nov 02, 2017 10:26 am

Maven authentication error (Error code 401)

Post by ncarp » Thu Nov 02, 2017 7:33 pm

Hi!
I am trying to build OpenKM from source with portable OpenKM development environment and I get some errors like this one:

Code: Select all

[INFO] ------------------------------------------------------------------------
[INFO] Building OpenKM Web Application 6.3.1-DEV
[INFO] ------------------------------------------------------------------------
[WARNING] The POM for com.dropbox.sdk:dropbox-client:jar:5.1.3 is missing, no dependency information available
[WARNING] The POM for net.sf:jodreports:jar:2.3.0 is missing, no dependency information available
Downloading: http://maven.openkm.com/maven2/commons-logging/commons-logging/1.2.1-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata commons-logging:commons-logging:1.2.1-SNAPSHOT/maven-metadata.xml from/to openkm.com (http://maven.openkm.com/maven2): Access denied to http://maven.openkm.com/maven2/commons-logging/commons-logging/1.2.1-SNAPSHOT/maven-metadata.xml. Error code 401, Unauthorized
Edit: Just adding more details

Code: Select all

Downloading: http://maven.openkm.com/maven2/commons-logging/commons-logging/1.2.1-SNAPSHOT/maven-metadata.xml
[DEBUG] onThrowable
org.sonatype.aether.connector.async.AuthorizationException: Access denied to http://maven.openkm.com/maven2/commons-logging/commons-logging/1.2.1-SNAPSHOT/maven-metadata.xml. Error code 401, Unauthorized
	at org.sonatype.aether.connector.async.AsyncRepositoryConnector.handleResponseCode(AsyncRepositoryConnector.java:472)
	at org.sonatype.aether.connector.async.AsyncRepositoryConnector.access$1800(AsyncRepositoryConnector.java:90)
	at org.sonatype.aether.connector.async.AsyncRepositoryConnector$GetTask$1.onCompleted(AsyncRepositoryConnector.java:750)
	at org.sonatype.aether.connector.async.CompletionHandler.onCompleted(CompletionHandler.java:180)
	at org.sonatype.aether.connector.async.CompletionHandler.onCompleted(CompletionHandler.java:39)
	at com.ning.http.client.providers.netty.NettyResponseFuture.getContent(NettyResponseFuture.java:244)
	at com.ning.http.client.providers.netty.NettyResponseFuture.done(NettyResponseFuture.java:269)
	at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.markAsDone(NettyAsyncHttpProvider.java:1560)
	at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.finishUpdate(NettyAsyncHttpProvider.java:1577)
	at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.messageReceived(NettyAsyncHttpProvider.java:1271)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:783)
	at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:149)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:783)
	at org.jboss.netty.handler.codec.http.HttpContentDecoder.messageReceived(HttpContentDecoder.java:131)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:783)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:302)
	at org.jboss.netty.handler.codec.replay.ReplayingDecoder.unfoldAndFireMessageReceived(ReplayingDecoder.java:522)
	at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:506)
	at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:443)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
	at org.jboss.netty.handler.codec.http.HttpClientCodec.handleUpstream(HttpClientCodec.java:77)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
	at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:349)
	at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:280)
	at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:200)
	at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
	at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
I am not used with Eclipse (Netbeans user) but it looks like more a server side error than wrong IDE use.

Kind regards,

Nuno Carpentier

jllort
Moderator
Moderator
Posts: 9702
Joined: Fri Dec 21, 2007 11:23 am
Location: Sineu - ( Illes Balears ) - Spain
Contact:

Re: Maven authentication error (Error code 401)

Post by jllort » Fri Nov 03, 2017 6:46 pm

The url is working http://maven.openkm.com/maven2/commons- ... -SNAPSHOT/ without authentication, can you check again and if it's possible, execute the first maven build from the command line.

ncarp
Fresh Boarder
Fresh Boarder
Posts: 5
Joined: Thu Nov 02, 2017 10:26 am

Re: Maven authentication error (Error code 401)

Post by ncarp » Fri Nov 03, 2017 6:56 pm

The URL you indicate is accessible, but the URL http://maven.openkm.com/maven2/commons- ... tadata.xml is prompting for username and password and is not accessible.
Can you point how to run maven build from command line on Windows 10 with portable OpenKM development environment.
Thanks.

jllort
Moderator
Moderator
Posts: 9702
Joined: Fri Dec 21, 2007 11:23 am
Location: Sineu - ( Illes Balears ) - Spain
Contact:

Re: Maven authentication error (Error code 401)

Post by jllort » Sat Nov 18, 2017 10:46 am

Sorry for the late answer, we will investigate it, seems some wrong privilege has been set here.

ncarp
Fresh Boarder
Fresh Boarder
Posts: 5
Joined: Thu Nov 02, 2017 10:26 am

Re: Maven authentication error (Error code 401)

Post by ncarp » Thu Dec 07, 2017 4:22 pm

Is there any news about this issue?

neftali
Fresh Boarder
Fresh Boarder
Posts: 3
Joined: Fri Dec 08, 2017 5:54 pm

Re: Maven authentication error (Error code 401)

Post by neftali » Fri Dec 08, 2017 6:09 pm

Hi.

I have the same issue. And, yes, it is right, the parent URL doesn't requieres credentials, but childs folders needs user and password.

I investigated a lot and I find in other post the supposed credentials, user: openkm and password: openkm, but don't works, that is wrong.

I need to solve this issue soon as possibble, I have implemented OpenKM and need urgently to build a Workflow for the go live.

Please your help.

Regards.

pavila
Moderator
Moderator
Posts: 3036
Joined: Tue Dec 11, 2007 6:02 pm
Location: Alicante, Spain
Contact:

Re: Maven authentication error (Error code 401)

Post by pavila » Mon Dec 11, 2017 5:51 pm

I would recommend compiling this source code at https://github.com/openkm/document-management-system which is the latest stable release. It compiles right.

Regards.

neftali
Fresh Boarder
Fresh Boarder
Posts: 3
Joined: Fri Dec 08, 2017 5:54 pm

Re: Maven authentication error (Error code 401)

Post by neftali » Tue Dec 12, 2017 8:18 am

Hi pavilla.

And I have invested a lot of time trying several ways to achieve an environment that works and by any means there is always something missing, such as old libraries, plugins or other products. My hope was with the portable environment. I just need the user and the password to the maven.openkm source, or someone from the OpenKM team that removes the permissions to the child folders. You could help me?

Regards.

pavila
Moderator
Moderator
Posts: 3036
Joined: Tue Dec 11, 2007 6:02 pm
Location: Alicante, Spain
Contact:

Re: Maven authentication error (Error code 401)

Post by pavila » Tue Dec 12, 2017 8:55 am

You don't need credentials to access our Maven repository. Simply you're trying to compile an old source code which tries to access to the wrong Maven repo. As I said, chechout the newest source code and just compile it.

Code: Select all

$ git clone https://github.com/openkm/document-management-system.git
$ cd document-management-system
$ ./build.sh

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest