central.maven.org doesn't exist

[nielsen-at-cgt]

# Download Jetty, verify the hash, and install, initialize a new base
RUN wget -q http://central.maven.org/maven2/org/eclipse/jetty/jetty-distribution/$jetty_version/jetty-distribution-$jetty_version.tar.gz \
    && echo "$jetty_hash  jetty-distribution-$jetty_version.tar.gz" | sha1sum -c - \
    && tar -zxvf jetty-distribution-$jetty_version.tar.gz -C /opt \
    && ln -s /opt/jetty-distribution-$jetty_version/ /opt/jetty-home

dig central.maven.org

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> central.maven.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48907
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;central.maven.org.             IN      A

;; AUTHORITY SECTION:
maven.org.              60      IN      SOA     ns-1965.awsdns-53.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400

;; Query time: 8 msec
;; SERVER: 172.29.0.2#53(172.29.0.2)
;; WHEN: Tue Mar 03 18:56:32 UTC 2020
;; MSG SIZE  rcvd: 133

[lrhazi]

Looks like replacing central.maven.org by repo1.maven.org, and http by https, should work.

[nielsen-at-cgt]

@lrhazi Thanks, I'll try it.

[lrhazi]

FYI, Jetty build was failing due to some github urls being invalid.. I upgraded the version and it seems to build OK:

    jetty_version=9.4.27.v20200227 \
    jetty_hash=6b683193067cd55c27b867f892a30e832d4e29a3 \

[lrhazi]

Sorry, simply upgrading jetty does not work!

[winstonhong]

@nielsen-at-cgt We just fixed the issues related to both central.maven.org doesn't exist and Jetty repo broken for Shibboleth IdP and SP based on Unicon's Shibboleth IdP and SP Docker image which have been cited in README.

I have validated all the the three (3) projects with the latest commit (i.e., commit 21) based on README tutorial on brand-new Ubuntu 18.04.

https://github.com/winstonhong/Shibboleth-SAML-IdP-and-SP