log-cache-cf-auth-proxy does not support HS256

[andrew-edgar]

Our UAA is setup with a valid HS256 symmetric key configuration. This works in the rest of CF but the log-cache-cf-auth-proxy fails to decode the keys and fails to authenticate with UAA because of this.

The UAA config using symmetric keys is valid and we are unable to move to asymmetric keys and so the new functionality in CF-CLI 6.50 is broken in our production envs.

We need HS256 supported ASAP as we are being forced to tell our customers they cannot upgrade to cf cli 6.50 and use the new "log-cache" until this is supported traffic controller cannot be deprecated and removed.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

[chendrix]

We have added a known issue to the 6.50.0 CLI release about this issue

https://github.com/cloudfoundry/cli/releases/tag/v6.50.0

[pianohacker]

We have a WIP at https://github.com/cloudfoundry/log-cache-release/tree/hs256 .

[pianohacker]

Fixed in b72d60f , will be in the next release.

[pianohacker]

Released in https://github.com/cloudfoundry/log-cache-release/releases/tag/v2.7.0 .