custom-security-filter should allow setting properties and referencing a bean

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 3.0.0-M4
  • Fix Version/s: 3.1.2, 3.2.0
  • Component/s: Core: Configuration
  • Labels:
    None
  • User impact:
    Low
  • Similar Issues:
    None

Description

  • without the capacity to set properties, you can't inject anything in the filter you're instantiating
  • without the capacity to reference a bean ('ref' attribute as an alternative to 'class' attribute), you have to copy/paste the custom-security-filter in all concerned endpoints.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dan Diephouse added a comment -

Fixed in 3.x r21741, 3.1.x 21742

Show
Dan Diephouse added a comment - Fixed in 3.x r21741, 3.1.x 21742
Hide
Permalink
Dan Diephouse added a comment -

Now, in 3.1.2/3.2.0 you can embed spring:propertys in the custom-security-filter. e.g.:

<custom-security-filter class="org.mule.security.UsernamePasswordAuthenticationFilter">
<spring:property name="password" value="#[header:inbound:pass]"/>
</custom-security-filter>

Show
Dan Diephouse added a comment - Now, in 3.1.2/3.2.0 you can embed spring:propertys in the custom-security-filter. e.g.: <custom-security-filter class="org.mule.security.UsernamePasswordAuthenticationFilter"> <spring:property name="password" value="#[header:inbound:pass]"/> </custom-security-filter>

People

  • Assignee:
    Dan Diephouse
    Reporter:
    David Dossot
Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: