attribute-resolver - loaded for every request?

[Kevin P. Foote]

The attribute-resolver stage will resolve all attributes for the given
principal. The filter stage will then remove (filter out) what goes to
the requesting entityId. 

So yes all attributes will be generated in your scenario. 

I believe this is also in the archives somewhere.. 

------
thanks
  kevin.foote

On Mon, 7 Nov 2011, Tim O'Connor wrote:

-> Hi - quick question - we are load testing our new system, and are running into issues.  
->  
-> firstly some background:
->  
-> - One of our SP's needs access to some external database's, so that is configured in attribute-resolver.xml.  
-> - We have a test SP for load testing - it does NOT made use of those user-defined attributes at all.
->  
-> What we are noticing, is that during the load test, connections are being made to the external database's, even though the load test SP does not make use of those attributes.
->  
-> Is it normal that for EVERY authentication, that the IdP will run though EVERY attribute that is defined in attribute-resolver.xml?
->