Load jwtClientAuthentication in uaa.yml

[strehle]

By mistake the variable jwtclientAuthentication was used in PR for clientAuthentication.
Documentation explains jwtClientAuthentication as entry

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/187161959

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

[peterhaochen47]

Before I look at this PR, I want to understand the original issue first. See comment.

[strehle]

@peterhaochen47

[peterhaochen47]

Thanks @strehle! I personally think that fixing the code to be aligned with the correct case-sensitive field jwtClientAuthentication as documented in our API doc (without being compatible with the incorrect jwtclientAuthentication) is okay, as it can be justified as a bug fix (and not as a breaking change).

What do you think? Are there a lot of adoptions of the incorrect jwtclientAuthentication on your side already?

[strehle]

What do you think? Are there a lot of adoptions of the incorrect jwtclientAuthentication on your side already?

No I am sure, that not many adoptions out with incorrect setting, but with this PR both settings would be used

But I asked me to change this PR so that only the correct setting is used?

[peterhaochen47]

What do you think? Are there a lot of adoptions of the incorrect jwtclientAuthentication on your side already?

No I am sure, that not many adoptions out with incorrect setting, but with this PR both settings would be used

But I asked me to change this PR so that only the correct setting is used?

Simply correcting the code to comply with the doc (without being compatible with the incorrect jwtclientAuthentication) would be my preference, as it's technically a bug fix, rather than an intentional field name migration. But if maintaining compatibility with the incorrect field is important to you, I'm okay with the current code too.

[strehle]

I'm okay with the current code too.

Ok, then I would like to stay with current code. In current code jwtClientAuthentication is used first, so no extra step if correct name is used, but for others jwtclientAuthentication would still work