CORS error when calling REST API with expired access token

[lorthirk]

Describe the bug
CORS Filter should not return an error when the token is expired, but a valid HTTP 401 response code is expected. This is probably due to the Shiro Filter being called, and returning an error, before the CORS filter can act, or due to a CORS Filter error during the execution

To Reproduce
Steps to reproduce the behavior:

1. Login with REST API and obtain an Access Token
2. Let the Access Token expire
3. Perform a REST API call after the token has expired
4. See error

Expected behavior
An HTTP 401 response should be returned

Version of Kapua
1.4.4

Type of deployment
[x] Local Vagrant deployment
[x] Docker
[x] Openshift (in its variants)
[x] Others

Main component affected
[ ] Console (in case of console please report info on which browser you encountered the problem)
[x] REST API
[ ] Message Broker
[ ] - Others