1 of 1 people found this helpful
Hi Jean Luc,
Some other solutions (not necessarily better):
- Deploy the ear file in exploded form, and use a deployment script that does a search & replace in the external-authentication-config.xml of the exploded ear.
- Make use of the multi-tenant functionality of the PicketLink Seam module. You can define multiple service providers in one configuration file, each with a different host name. This feature has originally been created for applications that need to serve different companies (tenants). Per request, the host name of the request is used to choose the corresponding service provider configuration. I expect that this also works for multi-environment deployments (for example development, test, production).
I prefer the first solution and use it for deploying to the development, test and production environment.
Option 1 doesn't work for us (the EARs are prepared and version-controlled prior to deployment) but the multi-tenant approach sounds interesting. I'll try it when I get to that stage.