Skip to content
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

UAA v75 CAT flakes #456

Merged
merged 1 commit into from
Feb 2, 2021
Merged

UAA v75 CAT flakes #456

merged 1 commit into from
Feb 2, 2021

Conversation

bruce-ricard
Copy link
Contributor

  • The test was expecting the UAA authorization code to only contain
    letters and numbers, which was a incorrect expectation. For example,
    as of today, the code can contain dashes "-".

  • The regex was updated so that the code can contain any character. If
    the UAA decides one day to add another CGI parameter to the redirect
    URL, the test won't break because of the "^&" in the regex.

  • The '\r' and '\n' are there to end the regex match at the end of the
    line.

  • For context, this is what an UAA API response looks like. See line 6
    the code we are trying to extract.

HTTP/2 302
cache-control: no-store
content-language: en-US
content-length: 0
date: Tue, 02 Feb 2021 22:10:17 GMT
location: http://example.com?code=gfCMdm9L3P # <- code here
strict-transport-security: max-age=31536000
x-content-type-options: nosniff
x-frame-options: DENY
x-vcap-request-id: 82abfda5-bf9c-4790-726a-b45d20d8883c
x-xss-protection: 1; mode=block
via: 1.1 google
alt-svc: clear

Are you submitting this PR against the develop branch?

Yes!

What is this change about?

Fixing the CATs compatibility with UAA.

Please provide contextual information.

https://cloudfoundry.slack.com/archives/C03FXANBV/p1612201884012700

What version of cf-deployment have you run this cf-acceptance-test change against?

latest

Please check all that apply for this PR:

  • introduces a new test --- Are you sure everyone should be running this test?
  • changes an existing test
  • requires an update to a CATs integration-config

Did you update the README as appropriate for this change?

  • YES
  • N/A

How many more (or fewer) seconds of runtime will this change introduce to CATs?

0

What is the level of urgency for publishing this change?

  • Urgent - unblocks current or future work
  • Slightly Less than Urgent

Tag your pair, your PM, and/or team!

@reedr3 , @peterhaochen47

* The test was expecting the UAA authorization code to only contain
  letters and numbers, which was a incorrect expectation. For example,
  as of today, the code can contain dashes "-".

* The regex was updated so that the code can contain any character. If
  the UAA decides one day to add another CGI parameter to the redirect
  URL, the test won't break because of the "^&" in the regex.

* The '\r' and '\n' are there to end the regex match at the end of the
  line.

* For context, this is what an UAA API response looks like. See line 6
  the code we are trying to extract.

HTTP/2 302
cache-control: no-store
content-language: en-US
content-length: 0
date: Tue, 02 Feb 2021 22:10:17 GMT
location: http://example.com?code=gfCMdm9L3P                # <- code here
strict-transport-security: max-age=31536000
x-content-type-options: nosniff
x-frame-options: DENY
x-vcap-request-id: 82abfda5-bf9c-4790-726a-b45d20d8883c
x-xss-protection: 1; mode=block
via: 1.1 google
alt-svc: clear

Co-Authored-By: Bruce Ricard <bricard@vmware.com>
@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/176773740

The labels on this github issue will be updated when the story is started.

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Feb 2, 2021

CLA Signed

The committers are authorized under a signed CLA.

Copy link
Contributor

@jamespollard8 jamespollard8 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - thanks again!

@jamespollard8 jamespollard8 merged commit 8f355e9 into develop Feb 2, 2021
@jamespollard8 jamespollard8 deleted the pr/code_regex branch February 2, 2021 23:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants