publish artifact to internal corporate nexus fails as unauthorized

126 views
Skip to first unread message

Fernando Racca

unread,
May 7, 2013, 2:13:09 PM5/7/13
to simple-b...@googlegroups.com
I'm trying to pubilsh a jar into an internal Nexus repository, but I'm getting Unauthorized replies. The credentials are the same than used for Maven, and I'm able to download dependencies using the same repo.

More details on this SO question:

http://stackoverflow.com/questions/16425639/sbt-publish-to-corporate-nexus-repository-unauthorized

Any help would be greatly appreciated.

Cheers,
Fernando

Fernando Racca

unread,
May 8, 2013, 6:10:24 AM5/8/13
to simple-b...@googlegroups.com
I'm still facing the same issue. is there any way to increase the level of logging on Ivy for publication?  I don't trust the authentictor since I'm also behind a company proxy.

also for reference, what does the credentials realm map to in terms of maven? is it the repository id or the repository name?

See more details in the SO question.

This is really blocking me, so any help appreciated

Thanks
Fernando

Alec Zorab

unread,
May 8, 2013, 6:21:53 AM5/8/13
to simple-b...@googlegroups.com


--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simple-build-t...@googlegroups.com.
To post to this group, send email to simple-b...@googlegroups.com.
Visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Fernando Racca

unread,
May 8, 2013, 6:36:45 AM5/8/13
to simple-b...@googlegroups.com
Thanks Alec

However, as documented in the question, I have already tried all the suggestions in that post.

Regards
Fernando

Alec Zorab

unread,
May 8, 2013, 6:40:14 AM5/8/13
to simple-b...@googlegroups.com
Your realm looks wrong to me. As noted in the answer I linked, it should probably be "Sonatype Nexus Repository Manager"

Fernando Racca

unread,
May 8, 2013, 7:49:42 AM5/8/13
to simple-b...@googlegroups.com
I don't know what realm corresponds to (instead of the repositoryId in maven which is clear, since it points to the user and password)

trying that setting didn't make a difference.

any idea how to increase level of logging for the publishing?

Fernando

Fernando Racca

unread,
May 8, 2013, 8:21:20 AM5/8/13
to simple-b...@googlegroups.com
I've been able to deploy using sbt-aether-deploy plugin. more details in the stack overflow questions 

There is something wrong between the proxy, ivy and nexus.

As far as i know SBT 0.12.3 uses Ivy 2.2.0, is that correct?

Any way to print what ivy is it doing?

Thanks

Robin Green

unread,
May 9, 2013, 3:46:05 AM5/9/13
to simple-b...@googlegroups.com
The realm is mentioned in a HTTP AUTH response header (named WWW-Authenticate I think); it is a name for a site or subsite for authentication purposes, and you can find out what realm the server is sending with any HTTP header inspection tool, such as Wireshark.
Reply all
Reply to author
Forward
0 new messages