-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create Orgs/Spaces Fails When Using Client Credentials #939
Comments
AT setup was failing due to our use of client credentials in CFJC's `UaaClient`, in combination with cloudfoundry/cf-java-client#939. All AT's passing locally now with this change.
* Remove log noise in ATs * Work around inability to create orgs with client credentials. Our AT setup was failing due to our use of client credentials in CFJC's `UaaClient`, in combination with cloudfoundry/cf-java-client#939.
* Remove log noise in ATs * Work around inability to create orgs with client credentials. Our AT setup was failing due to our use of client credentials in CFJC's `UaaClient`, in combination with cloudfoundry/cf-java-client#939.
* Remove log noise in ATs * Work around inability to create orgs with client credentials. Our AT setup was failing due to our use of client credentials in CFJC's `UaaClient`, in combination with cloudfoundry/cf-java-client#939.
* Remove log noise in ATs * Work around inability to create orgs with client credentials. Our AT setup was failing due to our use of client credentials in CFJC's `UaaClient`, in combination with cloudfoundry/cf-java-client#939. (cherry picked from commit 044c384)
HI, I am experiencing again this problem. when using @Value("${cf.clientId}")
private String clientId;
@Value("${cf.clientSecret}")
private String clientSecret;
//...
cloudFoundryOperations = DefaultCloudFoundryOperations.builder()
.cloudFoundryClient(useCloudFoundryClient())
.uaaClient(ReactorUaaClient.builder()
.connectionContext(DefaultConnectionContext.builder()
.apiHost(apiHost)
.build())
.tokenProvider(ClientCredentialsGrantTokenProvider.builder()
.clientId(clientId)
.clientSecret(clientSecret)
.build())
.build())
.build(); I get this exception:
Is it still actual or is it fixed? Thank you. It was closed 2 years ago, then opened again, would like to know the status of it. |
@Zavael Sorry, I do not believe that this has been resolved. I'm trying to get up-to-speed on this one as @twoseat is not on the team anymore. Given the fact this issue is open and PR #951 is not merged, I'm under the impression this is an outstanding issue. I will get this on the roadmap to be addressed. |
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.
The text was updated successfully, but these errors were encountered: