Joint SP configuration for two applications- attributePrefix conflict

[Klingenstein, Nate]

Alexander,

> The Dataverse application is coded to use an attribute prefix for Shibboleth attributes, whereas Drupal is not.  Considering this, is a Shared Entity SP configuration possible?

Sure, there are lots of ways you could do it.  You can change AJP to pass through other attributes, set multiple attributes in the SP from a single SAML attribute with attribute-map.xml, turn on header variables for the AJP implementation, change what Drupal is looking for, change what Dataverse is looking for...

It's hard for me to declare anything "best" here.  It's your environment.

It's all separate from most of the work you did.  You just need to choose which mapping you would like to use and own it.  It shouldn't break any of the other work you've done; this is just mapping the inbound information at the very end.

Hope this helps,
Nate.