Jitpack.io requiring Auth

[Travis Schmidt]

Is anyone else seeing this issue when building 5.1.x

FAILURE: Build failed with an exception.

* What went wrong:

Could not resolve all dependencies for configuration ':support:cas-server-support-duo-core:compileClasspath'.

> Could not resolve com.github.duosecurity:duo_client_java:master-SNAPSHOT.

  Required by:

      project :support:cas-server-support-duo-core

   > Could not resolve com.github.duosecurity:duo_client_java:master-SNAPSHOT.

      > Unable to load Maven meta-data from https://jitpack.io/com/github/duosecurity/duo_client_java/master-SNAPSHOT/maven-metadata.xml.

         > Could not GET 'https://jitpack.io/com/github/duosecurity/duo_client_java/master-SNAPSHOT/maven-metadata.xml'. Received status code 401 from server: Unauthorized

Seems that jitpack.io started requiring authorization yesterday afternoon.

[Misagh Moayyed]

Pull down the 5.1.x branch. That has the correct dependency definition I believe and you should be able to compare and adjust. It seems like jitpack changed the way artifacts are resolved, what with duo not releasing a proper jar for the duo client.

Sent with AquaMail for Android
http://www.aqua-mail.com

--
You received this message because you are subscribed to the Google Groups "CAS Developer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-dev+u...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/.

[Raymond Drew Walker]

I’m getting something similar for my mvn overlay builds for 5.0.6:

 

mvn clean install

[INFO] Scanning for projects...

[INFO]                                                                         

[INFO] ------------------------------------------------------------------------

[INFO] Building cas-overlay 1.0

[INFO] ------------------------------------------------------------------------

Downloading: https://jitpack.io/com/github/duosecurity/duo_client_java/master-SNAPSHOT/maven-metadata.xml

[WARNING] Could not transfer metadata com.github.duosecurity:duo_client_java:master-SNAPSHOT/maven-metadata.xml from/to jitpack (https://jitpack.io): Not authorized , ReasonPhrase:Unauthorized.

[WARNING] Failure to transfer com.github.duosecurity:duo_client_java:master-SNAPSHOT/maven-metadata.xml from https://jitpack.io was cached in the local repository, resolution will not be reattempted until the update interval of jitpack has elapsed or updates are forced. Original error: Could not transfer metadata com.github.duosecurity:duo_client_java:master-SNAPSHOT/maven-metadata.xml from/to jitpack (https://jitpack.io): Not authorized , ReasonPhrase:Unauthorized.

Downloading: https://jitpack.io/com/github/duosecurity/duo_client_java/master-SNAPSHOT/duo_client_java-master-SNAPSHOT.pom

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 1.480 s

[INFO] Finished at: 2017-07-17T14:24:17-07:00

[INFO] Final Memory: 23M/455M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal on project cas-overlay: Could not resolve dependencies for project org.apereo.cas:cas-overlay:war:1.0: Failed to collect dependencies at org.apereo.cas:cas-server-support-duo:jar:5.0.6 -> com.github.duosecurity:duo_client_java:jar:master-SNAPSHOT: Failed to read artifact descriptor for com.github.duosecurity:duo_client_java:jar:master-SNAPSHOT: Could not transfer artifact com.github.duosecurity:duo_client_java:pom:master-SNAPSHOT from/to jitpack (https://jitpack.io): Not authorized , ReasonPhrase:Unauthorized. -> [Help 1]

 

Course to correct this issue?

— 

Raymond Walker
Software Systems Engineer StSp.
ITS Northern Arizona University

[Matt Borja]

Hi all,

Check this PR: https://github.com/apereo/cas/pull/2757

or this commit: https://github.com/apereo/cas/pull/2757/commits/306867f160c74afcb24ec2552bfd8daa56221fe2

Also little "pro" tip: Check previous versions of the documentation (i.e. there are notable differences between 5.0.x and 5.1.x in some areas). This was how I discovered dupclient was still a dependency that simply did not get carried over in the 5.1.x docs.

We have Duo working successfully in a CAS 5.1.1 test instance. I can copy you on our gradle.build file when I get back to work in the AM if you want to see it, but basically this is the only additional entry we seemed to be missing.

Matt

[Raymond Drew Walker]

Matt,

 

This does not appear to be our issue.

 

I do have the correct repos included in our maven overlay as per documentation:

 

https://apereo.github.io/cas/5.0.x/installation/DuoSecurity-Authentication.html

 

ie.:

<repository>

    <id>duo</id>

    <url>https://dl.bintray.com/uniconiam/maven</url>

</repository>

<repository>

    <id>dupclient</id>

    <url>https://jitpack.io</url>

</repository>

 

As shown in the output of the original emails, jitpack.io is unable to get the duo_client_java metadata:

 

[WARNING] Could not transfer metadata com.github.duosecurity:duo_client_java:master-SNAPSHOT/maven-metadata.xml from/to duoclient (https://jitpack.io): Not authorized , ReasonPhrase:Unauthorized.

[WARNING] Could not transfer metadata com.github.duosecurity:duo_client_java:master-SNAPSHOT/maven-metadata.xml from/to jitpack (https://jitpack.io): Not authorized , ReasonPhrase:Unauthorized.

 

At this point we cannot move to 5.1.x.

 

How can we resolve this issue?

[Raymond Drew Walker]

All,

 

I tried the gradle 5.1.x overlay... it seems to have worked, but some oddities were involved:

 

Gradle:

$ gradle compileJava

Download https://jitpack.io/com/github/duosecurity/duo_client_java/-SNAPSHOT/maven-metadata.xml

Download https://jitpack.io/com/github/duosecurity/duo_client_java/-SNAPSHOT/duo_client_java--689b672b68-1.pom

Download https://jitpack.io/com/github/duosecurity/duo_client_java/duo-example-verify/-SNAPSHOT/maven-metadata.xml

Download https://jitpack.io/com/github/duosecurity/duo_client_java/duo-client/-SNAPSHOT/maven-metadata.xml

Download https://jitpack.io/com/github/duosecurity/duo_client_java/duo-example-verify/-SNAPSHOT/duo-example-verify--689b672b68-1.pom

Download https://jitpack.io/com/github/duosecurity/duo_client_java/duo-client/-SNAPSHOT/duo-client--689b672b68-1.pom

Download https://jitpack.io/com/github/duosecurity/duo_client_java/duo-example-admin/-SNAPSHOT/maven-metadata.xml

 

(notice the missing “MASTER” in the URLs... which do work!)

 

Then the Maven build for 5.0.6:

 

$ mvn -P local clean install

[INFO] Scanning for projects...

[INFO]                                                                         

[INFO] ------------------------------------------------------------------------

[INFO] Building cas-overlay 1.0

[INFO] ------------------------------------------------------------------------

Downloading: https://jitpack.io/com/github/duosecurity/duo_client_java/master-SNAPSHOT/maven-metadata.xml

Downloading: https://jitpack.io/com/github/duosecurity/duo_client_java/master-SNAPSHOT/maven-metadata.xml

[WARNING] Could not transfer metadata com.github.duosecurity:duo_client_java:master-SNAPSHOT/maven-metadata.xml from/to duoclient (https://jitpack.io): Not authorized , ReasonPhrase:Unauthorized.

[WARNING] Could not transfer metadata com.github.duosecurity:duo_client_java:master-SNAPSHOT/maven-metadata.xml from/to jitpack (https://jitpack.io): Not authorized , ReasonPhrase:Unauthorized.

 

Currently UNABLE to move to 5.1.x or migrate from maven to gradle.

Any ideas on how can this be resolved?

[Dmitriy Kopylenko]

I’ll “put some fuel to the fire”, so to speak. All of these shenanigans are caused by Duo project unable to properly publish their Java library to Maven central and/or Jcenter repositories (for whatever reason) etc.

See this: https://github.com/duosecurity/duo_java/issues/2 and this: https://github.com/duosecurity/duo_java/issues/1

Cheers,

D.

[Matt]

To be honest, we use Gradle exclusively for building the WAR file and per their docs so we haven't had this particular issue yet.

[Matt]

Looks like we're also specifying 5.1.1-SNAPSHOT in gradle.properties.

To build (Windows), we do: .\gradlew.bat clean build

Then look in .\cas\build\libs for cas.war.

Though, you indicated not being able to migrate to Gradle. Not sure if that's for business reasons or because of the issues you're having.

And yes, Duo is aware of the missing MASTER in -SNAPSHOT but like you saw, it seemed to replicate consistently in their repo and does still download.

Let me know if there's anything I can do to help.