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 Walker
Software Systems Engineer StSp.
ITS Northern Arizona University


From: <[email protected]> on behalf of Matt Borja <[email protected]>
Date: Tuesday, July 18, 2017 at 9:55 PM
To: Raymond Drew Walker <[email protected]>
Cc: Misagh Moayyed <[email protected]>, CAS Developers <[email protected]>
Subject: Re: [cas-dev] Jitpack.io requiring Auth

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

On Mon, Jul 17, 2017 at 2:31 PM, Raymond Drew Walker 
<[email protected]<mailto:[email protected]>> wrote:
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


From: <[email protected]<mailto:[email protected]>> on behalf of Misagh 
Moayyed <[email protected]<mailto:[email protected]>>
Date: Tuesday, June 13, 2017 at 2:55 PM
To: CAS Developers <[email protected]<mailto:[email protected]>>
Subject: Re: [cas-dev] Jitpack.io requiring Auth


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

On June 13, 2017 12:45:31 PM Travis Schmidt 
<[email protected]<mailto:[email protected]>> wrote:
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<http://jitpack.io> started requiring authorization 
yesterday afternoon.
--
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 [email protected]<mailto:[email protected]>.
Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/.
--
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 [email protected]<mailto:[email protected]>.
Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/.
--
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 [email protected]<mailto:[email protected]>.
Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/.

--
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 [email protected]<mailto:[email protected]>.
Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/.

-- 
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 [email protected].
Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/.

Reply via email to