URL Encoding using esapi.jar failed at Idp 3.1.1

[Surinaidu Majji]

Thanks for reply,
That's wrong. Whenever you get the urge to copy a jar, if it's not a JAAS
module or a JDBC driver, just stop.

1) but how IdP is using this jar(esapi.jar) in 2.4.0 version?

net.shibboleth.utilities.java.support.codec.HTMLEncoder
>> You mean to say  "net.shibboleth.utilities.java.support.codec.HTMLEncoder"
is replacement for  ESAPI.encoder(from esapi.jar)


On Thu, Jun 25, 2015 at 7:19 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 6/25/15, 5:46 AM, "users on behalf of Surinaidu Majji" <
> users-bounces at shibboleth.net on behalf of pioneer.suri at gmail.com> wrote:
>
>
>
> >        Since we used one of the API("ESAPI.encode()") from
> "esapi-2.1.jar" to encode the url, we have placed the esapi-2.1.jar in the
> "IDP" folder(idP-3.1.1)
>
> That's wrong. Whenever you get the urge to copy a jar, if it's not a JAAS
> module or a JDBC driver, just stop.
>
> An object of this class:
>
> net.shibboleth.utilities.java.support.codec.HTMLEncoder
>
>
> is exposed to every view in a variable called "encoder".
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150625/e232f1da/attachment.html>