Create Orgs/Spaces Fails When Using Client Credentials

Open
#939 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
api, authentication

Research direction

Start by tracing Java client Org and Space creation and the access-token handling described in the report. Compare the CLI resolution in issue 1418 and the linked solution, then verify that creation works with client-credentials authentication without an available username; related issues are explicitly out of scope.

Written by the indexing model from the issue text.

Description

bug operations triaged

Report from a customer:

"We’re trying to use client credentials auth everywhere as opposed to CF users. I hit a problem when trying to create an Org after making that change. The java client attempts to set the org manager user, by extracting the username of the currently authenticated user from the access token. Only now we’re using a client rather than a user, there is no username available…"

This issue has already been resolved in the CLI, we need to reflect their solution. Note that there are other related issues that will probably need handling separately.

Dominant language
Java
Stars
334
Forks
319
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudfoundry/cf-java-client

All issues in cloudfoundry/cf-java-client

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.