Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1168877

Summary: AuthenticationFilter class is missing in PicketLink
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Jan Tymel <jtymel>
Component: PicketLinkAssignee: Peter Skopek <pskopek>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Slavicek <pslavice>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: anmiller, bdawidow, cdewolf, kkhan, myarboro, psilva, pskopek, pslavice
Target Milestone: ER1   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:44:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1166062    

Description Jan Tymel 2014-11-28 09:55:57 UTC
Description of problem:
In PL federation was a possibility to use the servlet filter org.picketlink.authentication.web.AuthenticationFilter but this class is missing after PL upgrade in EAP 6.4.0.DR11. This bug is regression (works in 6.3.0)

Version-Release number of selected component (if applicable):
picketlink-api-2.5.3.SP13-redhat-1

How reproducible:
Use filter mapping in web.xml:
<filter>
    <filter-name>auth-filter</filter-name>
    <filter-class>org.picketlink.authentication.web.AuthenticationFilter</filter-class>
    <init-param>
        <param-name>authType</param-name>
        <param-value>BASIC</param-value>
    </init-param>
</filter>

Actual results:
java.lang.ClassNotFoundException: org.picketlink.authentication.web.AuthenticationFilter

Expected results:
Authentication using filter works as before PL upgrade

Comment 1 Pedro Igor 2014-11-28 11:09:15 UTC
Hi,

The functionality provided by the AuthenticationFilter was very limited. It was replaced by a much more flexible and powerful API for Http Security [1].

The configuration is easier and provides much more authentication options and also fine-grained authorization for your web application resources.

[1] http://docs.jboss.org/picketlink/2/latest/reference/html-single/#chap-Http_Security

Comment 2 Hynek Mlnarik 2014-11-28 11:26:10 UTC
Even though this might be a good direction for future and in the community, we need to preserve backward compatibility with EAP 6.3, as org.picketlink is public API according to [1] and customers should be able to rely on it.

[1] https://mojo.redhat.com/docs/DOC-137409

Comment 3 Pedro Igor 2014-11-28 11:47:00 UTC
Even when in Tech Preview ?

Comment 5 Pedro Igor 2014-11-28 13:48:47 UTC
I can easily include the AuthenticationFilter back to product version. Although we must disencourage its usage.

Makes sense ?

Comment 6 Hynek Mlnarik 2014-11-28 14:05:23 UTC
Yes, that would be a good way to do it. Thanks.

Comment 7 Pedro Igor 2014-11-28 19:43:50 UTC
Component was reverted. Should push to product branch on monday or so. Need to talk with Peter about the right branch to push my changes.

Comment 9 Kabir Khan 2014-12-02 12:59:49 UTC
Setting back to ASSIGNED, since that is the correct state until there is a 6.x PR with the component upgrade containing the change

Comment 10 Kabir Khan 2015-01-07 15:17:46 UTC
Should be fixed by PL upgrade 2.5.3.SP14 BZ1166062

Comment 11 Jan Tymel 2015-01-15 07:28:27 UTC
Verified in EAP 6.4.0.ER1