Re: IMPORTANT: Upcoming breaking changes in UAA V23/3.9.2/cf-release 248


Michael Fraenkel <michael.fraenkel@...>
 

How are the following required when they aren't used in bosh-lite?

*uaa.jwt.policy.keys:
*
* uaa.jwt.policy.active_key_id:*

How does one migrate from what we have to these?

- Michael

On 11/28/16 1:56 PM, Sree Tummidi wrote:
*Please read carefully if you are using UAA as _standalone_ or as a
_bosh release_ or part of _cf-release_*


Starting with UAA bosh release V23
<http://bosh.io/releases/github.com/cloudfoundry/uaa-release?version=23> which
packages UAA 3.9.2
<https://github.com/cloudfoundry/uaa/releases/tag/3.9.2> and
*cf-release 248 (in works)* the following *_properties have been made
required._*
*_
_*
These are standard artifacts which can be generated using openssl.
Please refer the topic here
<https://github.com/cloudfoundry/uaa-release#generating-a-self-signed-certificate> on
how to generate a self signed cert.
*_
_*

*login.saml.serviceProviderCertificate:*
description: "UAA SAML Service provider certificate. This is used for
signing outgoing SAML Authentication Requests"
example: |
-----BEGIN CERTIFICATE-----
-----END CERTIFICATE----
*login.saml.serviceProviderKey:*
description: "Private key for the service provider certificate."
example: |
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----

*uaa.jwt.policy.keys:*
description: "Map of key IDs and signing keys, each defined with a
property `signingKey`"
example:
key-1:
signingKey: |
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
* uaa.jwt.policy.active_key_id:*
description: "The ID of the JWT signing key to be used when signing
tokens."
example: "key-1"


Thanks,
Sree Tummidi
Staff Product Manager
Identity - Pivotal Cloud Foundry

Join {cf-dev@lists.cloudfoundry.org to automatically receive all group messages.