Our "We are sorry, but your account does not have access to this resource." was a process/documentation issue on my part. We have to update the group whitelist for the ezproxy ticket configuration on the backend to include every partner + stream group that is allowed. I haven't done this in a while, and it fell right out of my brain as a thing that needed doing. This should be on a punchlist for adding a new partner to proxy. It isn't required for bundle, since all bundle partners share the same ezproxy resource group.

Could you document the new-partner-addition process at https://github.com/WikipediaLibrary/TWLight/wiki/EZProxy-server?

Okay, I've updated the ticket configuration to include the current resource groups. It's scheduled for deployment in ~25 minutes.

Confirmed to now be working:

• Numerique Premium
• Erudit
• IWA Publishing
• Royal Society

Fold3 (at https://fold3.com) is now letting us through, but we're not being recognised by them.

EDP Sciences lets us through too, but I'm a bit confused about whether it's working or not. It looks, from clicking around there, like we're getting sent _out_ of the proxy quite quickly - to, for example, https://www.alr-journal.org/ (when clicking the journal name the proxy URL is removed from the header, and I'm sent straight to this URL)

https://github.com/WikipediaLibrary/TWLight/wiki/EZProxy-server now has content

EDP Sciences lets us through too, but I'm a bit confused about whether it's working or not. It looks, from clicking around there, like we're getting sent _out_ of the proxy quite quickly - to, for example, https://www.alr-journal.org/ (when clicking the journal name the proxy URL is removed from the header, and I'm sent straight to this URL)

Yeah, we'll need to know all of the domains that should proxied for users accessing this resource.

Yeah, we'll need to know all of the domains that should proxied for users accessing this resource.

I found this list of URLs from their journal list csv:

https://www.limnology-journal.org/
https://www.alr-journal.org/
https://www.aanda.org/
https://www.biologie-journal.org/
https://www.etp-journal.org/fr/
https://epljournal.edpsciences.org/
https://www.esaim-cocv.org/
https://www.esaim-m2an.org/
https://www.esaim-ps.org/
https://www.epjap.org/
https://www.europhysicsnews.org/
https://www.hel-journal.org/fr/
https://www.journaldephysique.org/fr/
https://www.mattech-journal.org/fr/
https://www.mmnp-journal.org/
https://www.mechanics-industry.org/
https://www.medecinesciences.org/fr/
https://www.metallurgical-research.org/
https://www.mov-sport-sciences.org/fr/
https://www.nss-journal.org/fr/
https://www.orthodfr.org/
https://www.pedagogie-medicale.org/
https://www.perspectives-psy.org/
https://www.psycho-clinique.org/
https://www.radioprotection.org/fr/
https://www.rairo-ro.org/
https://www.rairo-ita.org/
https://odf.edpsciences.org/
https://www.geotechnique-journal.org/

Also Fold3 looks to be on their end, I'm being sent updated instructions.

Okay, config updated. It's scheduled for deployment in ~20 minutes.

If you're interested, here's what fairly generic update to support those urls at both www.example.com and example.com looks like:
https://github.com/WikipediaLibrary/twlight_ezproxy/commit/a2e5772d9e155b27af7bac6705f297df4ca7eb26

Great, looks like that's working.

Doing a final review of all publishers.

Confirmed that - besides the two publisher-side issues - all access is working as expected.

Moving this to Done since there's nothing else we need to do on our end.

Rock's Backpages is fixed, Fold3 tracked in T256107