No. I am deploying the webapp manually on my own from src. 

My cas-management properties file is as such:
```
cas.host=https://mmoayyed-1933.unicon.net:8443
...
cas-management.host=${cas.host}
cas-management.prefix=${cas-management.host}/cas-management
```

This works perfectly fine when I attempt to navigate to https://mmoayyed-1933.unicon.net:8443/cas-management

If I switch to:
```
cas.host=https://mmoayyed-1933.unicon.net:8443
...
cas-management.host=${cas.host}
cas-management.prefix=${cas-management.host}/management
```

Navigating to https://mmoayyed-1933.unicon.net:8443/cas-management shows up with a 404. 

The context path by which the webapp is deployed by default is at cas-management. The reason it works in your demo is because you have forcibly made it available at `management` and that's perfectly fine for a custom setting, but we should still respect the defaults. An overlay method such as yours could of course be perfectly customized to make the context path be available at anything.