EPrints Technical Mailing List Archive

Message: #04478

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Re: Double Encoded URL

Hey Tim,

 

We essentially just setup our CAS authentication to work using the webserver authentication instructions. (http://wiki.eprints.org/w/Webserver_authentication)

 

We used the login-autocreate script and really just modified everything to use CAS instead of shibboleth. If you need more detail than that let me know and I can go deeper. Thanks again!

 

Rob

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Timothy Miles-Board
Sent: Thursday, July 09, 2015 2:07 AM
To: 'eprints-tech@ecs.soton.ac.uk'
Subject: [EP-tech] Re: Double Encoded URL

 

Hi Rob,

 

I've implemented CAS with EPrints a few times so I may be able to help.

 

Can you share some more details about how you've set things up?

 

Regards,

 

Tim

 

Timothy Miles-Board

Web & Repositories Development Specialist, University of London Computer Centre

020 7863 1342  |  07742 970 351  | timothy.miles-board@london.ac.uk | @drtjmb

The University of London is an exempt charity in England and Wales

 

From: eprints-tech-bounces@ecs.soton.ac.uk <eprints-tech-bounces@ecs.soton.ac.uk> on behalf of Glover, Robert W. <RWGLOVER@fortlewis.edu>
Sent: 08 July 2015 5:33 PM
To: 'eprints-tech@ecs.soton.ac.uk'
Subject: [EP-tech] Double Encoded URL

 

Hello,

 

We have recently tried to implement webserver authentication via CAS to our 3.3.14 development instance. We have it working to the point that when logging in it redirects to our CAS login page but the url is double encoded(see below) and because of the double encoding the redirect back to our eprints instance doesn’t occur. 

 

https%253A%252F%252Ffortworks-dev.fortlewis.edu%252Fsecure%252Fcgi%252Fusers%252Fhome

 

It seems that the CAS auth module is encoding it once and then eprints is then encoding it again.  Is there a way to get eprints to realize that the url has already been encoded and to not encode it again?

 

Rob Glover

Systems Engineer

Fort Lewis IT Department

rwglover@fortlewis.edu

(970)247-7413