A customer (actually using RH-SSO 7.0) is asking about the following request :

<quote>

When using RH-SSO and EAP, one can secure deployments with a subsystem configuration like :

<secure-deployment name="application.war">
<realm>My-Realm</realm>
<resource>my-resource</resource>
<public-client>true</public-client>
<realm-public-key>[...key...]</realm-public-key>
<auth-server-url>http://hostname:port/auth</auth-server-url>
<ssl-required>ALL</ssl-required>
</secure-deployment>

The secure deployment name matches the deployment name.

Our practice is to have version in the name of the war (standard maven builds) : application-x.y.z.war

Which means that with every new deployment, we need to edit the secure-deployment configuration.

Or we have to give up the naming scheme and stick to a no-version application.war name.

Would it be possible to have a wildcard match for this configuration ?

For example : <secure-deployment name="application-*.war">

It would be applied to any deployment application-1.0.0.war, application-1.0.1.war and so on.

</quote>

Is this an acceptable RFE ?