Reputation: 31
We have a use case where all the apps staged and run with the WebSphere Liberty Profile Buildpack have to authenticate with LDAP and a SiteMinder SSO Proxy.
We have implemented this feature by configuring a TAI in Liberty and pushing the app as a server package.
We don't want to push server packages for each app
How should we package the features like
ldapRegistry-3.0
, the TAIlibrary
and the associatedtrustAssociation
server configuration so that all the apps staged by the buildpack inherit this configuration without pushing server packages. Can this be done with a user feature ?
-cheers, Rohit Kelapure
Upvotes: 2
Views: 272
Reputation: 96
I can think of three options:
server.xml
with your configuration into a configDropins directory of the Liberty server. Upvotes: 2
Reputation: 1441
Unfortunately, there's no other way to setup the other security mechanisms (TAI Library & trustAssociateion server config) without pushing a server package or pushing a server directory. See (1) for more details on protecting resources in Liberty.
If you were just adding Liberty features or needed to specify a different set of features, then you could set the JBP_CONFIG_LIBERTY environment variable and restage the app:
$ cf set-env myapp JBP_CONFIG_LIBERTY "app_archive: {features: [ldapRegistry-3.0]}"
$ cf restage myapp
For more information on other options for pushing Liberty applications, see (2) below.
(2) https://www.ng.bluemix.net/docs/starters/liberty/index.html#optionsforpushinglibertyapplications
Upvotes: 0