Is uaa.login.client_secret unnecessary? #85
Comments
|
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/141038853 The labels on this github issue will be updated when the story is started. |
|
Hey @geofffranks. Great find. Thanks for pointing this out. I'll prioritize this story. |
cf-gitbot
added
scheduled
in progress
delivered
accepted
and removed
unscheduled
scheduled
in progress
delivered
labels
|
We've made the fix and accepted the story, so I'm closing the issue. |
ryankilroy
pushed a commit
to ryankilroy/bosh-deployment
that referenced
this issue
Jul 9, 2019
- Similar issue in cf-deployment: cloudfoundry/cf-deployment#85
This was referenced Jul 9, 2019
boergsen
added a commit
to boergsen/docs-bosh
that referenced
this issue
Nov 4, 2019
* add `admin` user to `clients` section (see https://github.com/cloudfoundry/bosh-deployment/blob/85d2f2122bfc2c1f5184c4b10224705fe22d8113/uaa.yml#L40) * remove outdated property `login` (see cloudfoundry/cf-deployment#85)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The job properties for the UAA in cf-deployment.yml includes a
uaa.login.client_secretproperty, but that is no longer a property listed in the UAA spec, and looks to have been removed in cloudfoundry/uaa-release@a33a1f3Should this be removed from the manifest, and replaces with a login client defined in
uaa.clients? Is the login client no longer required inuaa.clientseither?The text was updated successfully, but these errors were encountered: