cloudfoundry / cloudfoundry/stratos

Connect endpoint failed on some platforms.

Open
#4,894 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community
Dominant language
TypeScript
Stars
267
Forks
137
Avg merge
5h 14m
Merged PRs (30d)
77

Description

Stratos Version

4.4.0

Frontend Deployment type
  • Cloud Foundry Application (cf push)
  • Kubernetes, using a helm chart
  • Docker, single container deploying all components
  • npm run start
  • Other (please specify below)
Backend (Jet Stream) Deployment type
  • Cloud Foundry Application (cf push)
  • Kubernetes, using a helm chart
  • Docker, single container deploying all components
  • Other (please specify below)
Expected behaviour

It can connect to the endpoint successfully in win10 +chrome 88 & win2019 + chrome 89.

Actual behaviour

It always failed to connect to the endpoint with Bad credentials(401). See attached image for details.

Steps to reproduce the behavior
1. Click '+' icon to register a new Endpoint
2. Select Cloud Foundry as the type of the endpoint to register
3. Input characters in Name, for example : test
4. Input a valid Endpoint address
5. Check 'Skip SSL validation for the endpoint'
6. Click 'Register' button
7. Click 'Connect' button
8. Try step1-7 in two VMs:  win10 +chrome 88 & win2019 + chrome 89
Log output covering before error and any error statements
Insert log hereCopy

image

Workaround:
It works fine in win2012 + chrome.

Detailed Description
Context
Possible Implementation

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the endpoint registration and connection steps in Chrome 88 on Windows 10 and Chrome 89 on Windows Server 2019, then compare them with the working Windows Server 2012 case. Use the 401 Bad credentials response and the endpoint connection flow as the investigation boundary; done means the endpoint connects successfully on the affected platforms.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, helm, kubernetes, typescript
Domain
cloud, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.